Is the Bbcbasic Testgraph MCP server down?

mcp-registry/io.github.bbcbasic/testgraph · v3.24.0-alpha

Also listed as glama/bbcbasic/testgraph

healthy
Last checked 2026-10-18 04:07 UTC · handshake 157ms

As of 2026-10-18 04:07 UTC, the Bbcbasic Testgraph MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 9 minutes.

uptime (30d checks)
100%
checks observed
3,657
outages (90d)
2
tools
37

Shared semantic graph for AI reviews, classification and structured memory across AI assistants.

Install Bbcbasic Testgraph MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http bbcbasic-testgraph-mcp-server https://testgraph.21dle.co.uk/mcp-v2

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "bbcbasic-testgraph-mcp-server": {
      "type": "http",
      "url": "https://testgraph.21dle.co.uk/mcp-v2"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 4 warning(s) across 37 tool(s); ~12,106 tokens of tool definitions.
Scores higher than 14% of 15,354 MCP servers Glimind has audited.
Its tool list costs an agent ~12,106 tokens per session — more than 85% of servers.
76 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas87
Descriptions30
Safety hints100
Token cost87
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (5)

2 tool definition(s) exceed ~1,200 tokens each (largest: save_experience, ~2,513).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~3,581 tokens every session. How to fix →

Tools: save_experience, enrich_subject · saves ~3,581 tokens/session

146 parameter(s) across 34 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: affirm_subject_classification, assert_location, claim_deliberation, correct_subject_fact, create_deliberation and 29 more

2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: assert_location, correct_subject_fact

Handshake + tools/list takes ~1,788 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 34 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.bbcbasic%2Ftestgraph/fixes

assert_location 1 change
{
  "name": "assert_location",
  "description": "Add a governed location assertion for an existing eligible subject. Resolve the subject and any existing Place first. New Places require a stable canonical key plus a durable identifier. Every assertion requires source provenance. Coordinates are WGS84 only and are never silently geocoded. WORKFLOW PRECONDITION: for an existing subject, the server checks classification before mutation. The authenticated user may always enrich a subject they own or one attached to their own non-deleted review wit",
  "inputSchema": {
    "type": "object",
    "required": [
      "subject_id",
      "predicate",
      "source",
      "idempotency_key"
    ],
    "properties": {
      "value": {
        "type": "string"
      },
      "source": {
        "type": "object",
        "additionalProperties": true
      },
      "valid_to": {
        "type": "string",
        "format": "date-time"
      },
      "predicate": {
        "enum": [
          "located_in",
          "contained_in",
          "published_address",
          "postcode",
          "position"
        ],
        "type": "string"
      },
      "qualifiers": {
        "type": "object",
        "default": {},
        "additionalProperties": true
      },
      "subject_id": {
        "type": "string",
        "format": "uuid"
      },
      "valid_from": {
        "type": "string",
        "format": "date-time"
      },
      "visibility": {
        "enum": [
          "private",
          "unlisted",
          "public"
        ],
        "type": "string",
        "default": "private"
      },
      "observed_at": {
        "type": "string",
        "format": "date-time"
      },
      "object_place": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "place_kind": {
            "type": "string"
          },
          "subject_id": {
            "type": "string",
            "format": "uuid"
          },
          "identifiers": {
            "type": "object",
            "additionalProperties": true
          },
          "canonical_key": {
            "type": "string"
          }
        },
        "additionalProperties": false
      },
      "idempotency_key": {
        "type": "string",
        "maxLength": 200,
        "minLength": 8
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Assert an evidence-backed location"
}
correct_subject_fact 1 change
{
  "name": "correct_subject_fact",
  "description": "Replace one incorrect identifier or attribute using the stable subject ID. The current value must match expected_value, authoritative evidence and a reason are mandatory, and the server preserves an immutable correction record in subject provenance. Use enrich_subject for missing facts; never use this operation merely to add a value. WORKFLOW PRECONDITION: for an existing subject, the server checks classification before mutation. The authenticated user may always enrich a subject they own or one",
  "inputSchema": {
    "type": "object",
    "required": [
      "subject_id",
      "field_root",
      "field_path",
      "expected_value",
      "corrected_value",
      "evidence_sources",
      "reason",
      "idempotency_key"
    ],
    "properties": {
      "reason": {
        "type": "string",
        "minLength": 1
      },
      "field_path": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]+(?:\\.[A-Za-z0-9_-]+)*$",
        "description": "Dot-separated path below field_root."
      },
      "field_root": {
        "enum": [
          "identifiers",
          "attributes"
        ],
        "type": "string"
      },
      "subject_id": {
        "type": "string",
        "format": "uuid"
      },
      "expected_value": {
        "type": "string"
      },
      "corrected_value": {
        "type": "string"
      },
      "idempotency_key": {
        "type": "string",
        "maxLength": 200,
        "minLength": 8
      },
      "evidence_sources": {
        "type": "array",
        "items": {
          "type": "string",
          "minLength": 1
        },
        "maxItems": 20,
        "minItems": 1
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": true
  },
  "title": "Correct an existing subject fact"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.bbcbasic/testgraph"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.bbcbasic/testgraph"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bbcbasic%2Ftestgraph.svg)](https://glimind.com/server/mcp-registry%2Fio.github.bbcbasic%2Ftestgraph?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.bbcbasic%2Ftestgraph?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bbcbasic%2Ftestgraph.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bbcbasic%2Ftestgraph.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.bbcbasic%2Ftestgraph?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b0c244c663424a49…, first seen 2026-10-17, included at leaf 11752 of 20,279. Version history · verify what your client received.

Tools (37)

Compare: most reliable ml servers · most reliable knowledge servers · most reliable communication servers · most reliable retrieval servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Bbcbasic Testgraph MCP server down right now?

As of 2026-10-18 04:07 UTC, the Bbcbasic Testgraph MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 9 minutes.

How many tools does Bbcbasic Testgraph MCP server provide?

Bbcbasic Testgraph MCP server advertises 37 tools, including affirm_subject_classification, assert_location, claim_deliberation, correct_subject_fact, create_deliberation.

How do I install Bbcbasic Testgraph MCP server?

Point your MCP client at this streamable-http endpoint: https://testgraph.21dle.co.uk/mcp-v2

Is the Bbcbasic Testgraph MCP server safe to connect to an AI agent?

Glimind scanned all 37 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Bbcbasic Testgraph MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.