Responded16 / 22 checks passed
Search excessionlabs.ai, the site of Excession Labs, a security lab, and request a security test.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 71 ms · Last checked
Independent monitoring
Health & checks
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 3 | 1 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Inspect individual checks 22 recorded
Core
- Pass
- Pass
- Pass
- Pass
- Pass
Performance
- Not measured
- Not measured
- Not measured
- Not measured
Access
- Pass
- Not measured
- Not measured
Tools
- Pass
- Pass
- Pass
- Fail
Publisher
- Pass
- Pass
- Fail
- Not measured
- Pass
- Not measured
Start using CorpusFetch
Connect to this server
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http corpusfetch https://mcp.corpusfetch.com/mcpCapabilities
Tools 6
corpusfetch_fetch_record
Fetch the full resolved experience record. Format `md` (~1,500 tokens, includes reasoning) or `py` (~300 tokens, zero-prose executable invariants).
Discoveredcorpusfetch_fetch_warrant
Fetch the compact ~220-token precondition seal for a resolved record. Always call this before `corpusfetch_fetch_record`—check the seal first; if it fails, the record does not apply to your current state.
Discoveredcorpusfetch_lookup_exception
Look up operational experience for an exact Python exception class (e.g., KeyError, TimeoutError, ConnectionError). Use when you encounter an unexpected runtime error and need an empirically verified boundary decision rather than a guess. Prefer `corpusfetch_search` when you have a symptom description but not an exact exception name.
Discoveredcorpusfetch_lookup_symptom
Look up operational experience for a specific runtime symptom or boundary failure (e.g., UNICODE_HOMOGLYPH_OR_MOJIBAKE). Use when facing an ambiguous failure state or unbounded reasoning loop. Prefer `corpusfetch_search` if you only have a loose description.
Discoveredcorpusfetch_request_experience
Request a new operational experience when `corpusfetch_search` returns no match. The corpus will generate and publish a record for your specific error or symptom within minutes. Use this instead of guessing when the problem is novel and no existing record applies.
Discoveredcorpusfetch_search
Search operational records for distributed systems failures, AI agent protocol issues, MCP/A2A problems, database anomalies, concurrency bugs, and runtime errors. Use when the user's problem involves infrastructure, agent-to-agent coordination, authentication, memory management, or observability. Do not use for general programming questions—only for boundary decisions and failure modes that have been empirically recorded.
DiscoveredRecent measurements
Probe history
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 338 ms | 6 |