Fact-check claims against live web sources: verdict, consensus, cited sources, PII redaction.
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://trinity-v2-mcp.fly.dev/mcp4 tools · 314msmulti_source_validatorVerify a factual claim against multiple live web sources (Brave). Returns a JSON object with a verdict (supported / contradicted / unverified), a 0-1 consensus score, short reasoning, and the actual cited sources (ref, title, url). Judges only from retrieved sources — never fabricates. 'contradicte…Verify a factual claim against multiple live web sources (Brave). Returns a JSON object with a verdict (supported / contradicted / unverified), a 0-1 consensus score, short reasoning, and the actual cited sources (ref, title, url). Judges only from retrieved sources — never fabricates. 'contradicte…
| Parameter | Type | Description |
|---|---|---|
| claim* | string | The factual claim to verify against multiple web sources. |
| count | integer | How many web sources to consult (default 5, max 10). |
pingLiveness probe. Returns 'pong' plus any supplied message.Liveness probe. Returns 'pong' plus any supplied message.
| Parameter | Type | Description |
|---|---|---|
| message | string | null | Optional message echoed back, to verify round-trip serialization. |
privacy_shield_redactRedact personally identifiable information (PII) from text — emails, phone numbers, IDs, names, etc. Returns the masked text plus a count of what was redacted by type. Privacy-by-default for research workflows.Redact personally identifiable information (PII) from text — emails, phone numbers, IDs, names, etc. Returns the masked text plus a count of what was redacted by type. Privacy-by-default for research workflows.
| Parameter | Type | Description |
|---|---|---|
| text* | string | The text to scan and redact for personally identifiable information. |
structured_brief_synthesizerSynthesize multiple sources into a structured, cited brief. format: 'synthesis' (narrative), 'summary' (bullets), or 'integrated' (how sources connect). Cites inline as [n]; never invents facts beyond the sources.Synthesize multiple sources into a structured, cited brief. format: 'synthesis' (narrative), 'summary' (bullets), or 'integrated' (how sources connect). Cites inline as [n]; never invents facts beyond the sources.
| Parameter | Type | Description |
|---|---|---|
| format | string | Output format: "synthesis" (narrative, default), "summary" (bullets), or "integrated" (shows how sources logically connect). |
| sources* | array | Sources to integrate (each with a title and content). |
4 of 4 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.
Fact-check claims against live web sources: verdict, consensus, cited sources, PII redaction.
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.