Read what the catalog actually published.
We read the published tool names and required fields, then flag findings when the catalog sent the run the wrong way. This is not a named-host matrix.
Catalog versus the run
Published
- search · q: string
- fetch · url: uri
- write · id required
Used
- search.q sent
- fetch.url sent
- write.id never sent
The latest Connection catalog. Not a host matrix.
The catalog is a guide, not a proof.
Listed is not called. A finding is a field or name that sent the run the wrong way. Host reach lives on Host Compatibility.
The published guide
tools/list and the input schemas, then whether the AgentStatus run could use what was published.
The catalog
Tool names from tools/list plus required fields from each tool's input schema, with the published type and format.
Findings
Two names for the same work. A required field typed only as a string. A description that disagrees with the schema. A field the catalog required and the run never sent.
Not a host matrix
How Cursor or VS Code reached the server. That is Host Compatibility. Contract does not need a named host profile.
Use what was published
The run either could follow the guide, or the guide sent it the wrong way.
Required fields
What the schema said was required, and whether the run sent it. A missing required field is a finding.
Last catalog
Contract is filled by the latest Connection catalog, not by its own host matrix.
Neutral when nothing is published
No output schema is not a warning. We do not invent a contract the server never wrote.
When we flag
A finding is a field or name that sent the run the wrong way.
Two names, same work
Two catalog names for the same work are a finding.
Description versus schema
A description that disagrees with the schema is a finding.
We do not invent an id
A later tool waiting on an empty earlier list is only a finding when a named earlier list supplied that id.
FAQ
Common questions
| Question | Answer |
|---|---|
| Is Contract a host matrix? | No. Contract is the published catalog versus the AgentStatus run. How Cursor or VS Code reached the server is Host Compatibility. |
| Where does the catalog come from? | The latest Connection tools/list. Contract does not run a second named-host walk. |
| Do missing output schemas fail the contract? | No. No output schema is neutral. We do not warn when the server publishes none. |
If the catalog lies,every host inherits the lie.
Paste the MCP URL. We read what you published, then whether the run could follow it.
Cover your blind spots