Does a cited URL exist, and does the source name what your claim names? Two answers.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://exmachina-ai.fly.dev/verify2 tools · 82mscheck_citationFetch a URL and report whether it exists, and whether the source names the same entity as the claim you attach to it. These are two different questions and conflating them is the failure this exists to catch: a URL can return 200 and describe a different gene entirely. No account needed, nothing is…Fetch a URL and report whether it exists, and whether the source names the same entity as the claim you attach to it. These are two different questions and conflating them is the failure this exists to catch: a URL can return 200 and describe a different gene entirely. No account needed, nothing is…
| Parameter | Type | Description |
|---|---|---|
| url* | string | The citation to check. http(s) only; private and loopback addresses are refused. |
| claim | string | Optional. The text that cites it — the sentence or finding this URL is meant to support. Without it you only learn whether the URL exists, which is the weaker… |
verdict_meaningsThe exact semantics of every status and relevance value, including what this checker cannot determine. Read once before trusting a verdict.The exact semantics of every status and relevance value, including what this checker cannot determine. Read once before trusting a verdict.
No input schema was published for this tool.
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Does a cited URL exist, and does the source name what your claim names? Two answers.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.