io.github.oathlayer/oathlayer
REMOTE · MCP.OATHLAYER.COM
Verify AI outputs against real sources. Returns a trust signal and permanent doc number.
Available components
Last scanned (22 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 397 tokens (~397/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +7
- Authorization: unverified → partial ▲ security
- Tool “verify_output” rewrote its description, which is the text the model reads security
- Schema quality: 283 → 397 ▼ functional
- “verify_output” reworded the description of “apiKey” cosmetic
- “verify_output” made “apiKey” optional cosmetic
- 30 Oct 26 −1
- Tool “verify_output” rewrote its description, which is the text the model reads security
- 26 Oct 26 −1
- Tool “verify_output” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “verify_output” reworded the description of “apiKey” cosmetic
- “verify_output” reworded the description of “question” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.oathlayer.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oathlayer.com | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6e17c25f6481414b13f090b12a7398ec |
| SANs: oathlayer.com, mcp.oathlayer.com, *.mcp.oathlayer.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.oathlayer.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| oathlayer.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.oathlayer.com | Verified | 200 | |
| http (plaintext) | http://mcp.oathlayer.com | HTTPS enforced | 301 | https://mcp.oathlayer.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
verify_output ~397
Verify an AI answer against real sources before anyone acts on it. Send a question; Oathlayer answers it, checks the answer against independent sources, and returns the answer, a state, a plain-language message (the tag), a color, and a permanent doc number anyone can verify free at oathlayer.com/verify. Tags: Verification Successful - Oath Approved (green); Verification Threshold Not Met (blue); Various Perspectives Apply (purple); Complex Question - Threshold Reserved; Clarity Needed to Continue (pink). Legal citations also get a citation tag: confirmed on official sources (green), found only on unofficial sites (blue), mismatched with the correct citation shown (coral), or not found in available sources (golden brown). Citation answers also include a short label: Confirmed, Unofficial, Mismatched or Not found. Oathlayer reports what happened; it does not judge right or wrong. Works on any topic and with any AI model. Costs one credit per completed check; errors and wrong keys cost nothing. Requires an API key from oathlayer.com. If a message starts with Oathlayer: then use this tool to check the question that follows. When showing the result to the user, always use exactly this layout, one item per line, as plain text with no bold: 'Question:' then the question that was checked, 'Answer:' then the answer from Oathlayer, 'Verification tag:' then the tag message, 'Doc ID number:' then the doc number. Do not add anything else, such as how many credits were used.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Your Oathlayer API key from oathlayer.com. Only needed if the key was not added when connecting Oathlayer. Each completed check uses one credit. |
| question | string | yes | The question to verify, in plain words (for a legal citation, include the full case name and citation). Spanish questions are supported. |
No output schema declared.
No examples provided.
How do I install the io.github.oathlayer/oathlayer MCP server?
io.github.oathlayer/oathlayer is a hosted endpoint at https://mcp.oathlayer.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.oathlayer.com
claude mcp add --transport http oathlayer-oathlayer 'https://mcp.oathlayer.com/'
What is the io.github.oathlayer/oathlayer MCP server?
io.github.oathlayer/oathlayer is an MCP server listed in the public MCP registry as io.github.oathlayer/oathlayer. Verify AI outputs against real sources. Returns a trust signal and permanent doc number. This page covers its hosted endpoint (https://mcp.oathlayer.com).
Is the io.github.oathlayer/oathlayer MCP server safe to use?
io.github.oathlayer/oathlayer scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.oathlayer/oathlayer MCP server expose?
io.github.oathlayer/oathlayer exposes 1 tool: verify_output. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.
Does the io.github.oathlayer/oathlayer MCP server require authentication?
No. We connected to io.github.oathlayer/oathlayer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.oathlayer/oathlayer MCP server still maintained?
io.github.oathlayer/oathlayer is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.