mcp-registry/io.github.lexbritten/probe · v0.1.0
As of 2026-10-26 23:16 UTC, the Lexbritten Probe MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
Point your MCP client at this streamable-http endpoint: https://probe-evidence.probe-lab.workers.dev/mcp
1 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.lexbritten%2Fprobe/fixes
{
"name": "probe_history",
"description": "Retrieve up to 20 persisted observations for an existing Probe experiment ID without making a new HTTP request. Use after verify_http_claim to inspect repeated results, PASS/FAIL/ERROR counts, agreement, or whether the observed verdict changed between the two latest decisive observations. This is historical evidence lookup, not a current live verification; use verify_http_claim when freshness or present endpoint behavior matters.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"probe_id"
],
"properties": {
"limit": {
"type": "integer",
"default": 10,
"maximum": 20,
"minimum": 1,
"description": "Maximum number of newest stored observations to return, from 1 through 20."
},
"probe_id": {
"type": "string",
"pattern": "^[a-f0-9]{64}$",
"description": "The 64-character lowercase hexadecimal Probe experiment ID returned by verify_http_claim."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Inspect Historical HTTP Evidence"
}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.lexbritten/probe"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.lexbritten/probe"}) over MCP.
verify_http_claim ~827 tokensprobe.history ~256 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fio.github.lexbritten%2Fprobe?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.lexbritten%2Fprobe?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lexbritten%2Fprobe.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.lexbritten%2Fprobe.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.lexbritten%2Fprobe?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:eadde7c0d8b7313f…, first seen 2026-10-17, included at leaf 550 of 76,031. Version history · verify what your client received.
Compare: most reliable web servers · most reliable data servers
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.
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"
}
}
}
As of 2026-10-26 23:16 UTC, the Lexbritten Probe MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Lexbritten Probe MCP server advertises 3 tools, including probe, probe.history, verify_http_claim.
Point your MCP client at this streamable-http endpoint: https://probe-evidence.probe-lab.workers.dev/mcp
Glimind scanned all 2 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.
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.