Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dk.humanified/trinity-research

REMOTE · TRINITY-V2-MCP.FLY.DEV · SCANNED SEP 21

Fact-check claims against live web sources: verdict, consensus, cited sources, PII redaction.

0 this week 79 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 395 tokens (~98/item across 4 items; 4 tools + 0 resources), lean.Pass
  • 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Install

How do I install the dk.humanified/trinity-research MCP server?

dk.humanified/trinity-research is a hosted endpoint at https://trinity-v2-mcp.fly.dev/mcp, 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 · trinity-v2-mcp.fly.dev

# add to Claude Code
claude mcp add --transport http dk-humanified-trinity-research 'https://trinity-v2-mcp.fly.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dk-humanified-trinity-research": {
      "url": "https://trinity-v2-mcp.fly.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dk-humanified-trinity-research": {
      "type": "http",
      "url": "https://trinity-v2-mcp.fly.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dk-humanified-trinity-research]
url = "https://trinity-v2-mcp.fly.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dk-humanified-trinity-research": {
      "type": "remote",
      "url": "https://trinity-v2-mcp.fly.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dk-humanified-trinity-research --url 'https://trinity-v2-mcp.fly.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dk-humanified-trinity-research:
    url: "https://trinity-v2-mcp.fly.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dk-humanified-trinity-research": {
      "Transport": "http",
      "Url": "https://trinity-v2-mcp.fly.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dk-humanified-trinity-research -t streamable-http -u 'https://trinity-v2-mcp.fly.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "dk-humanified-trinity-research": {
      "type": "http",
      "url": "https://trinity-v2-mcp.fly.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 3 Sept 26 0
    • Stability: 0.97 → pass security
  • 2 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Aug 26 0
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Schema quality: 30 → 98 functional
    • Schema quality: unverified → fail functional
    • Tool coverage: unverified → 100 functional
    • Schema quality: good → excellent functional
    • Stability: fail → 0.53 functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

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 21 Sept 2026 · Probed https://trinity-v2-mcp.fly.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fly.dev CN=YE1,O=Let's Encrypt,C=US 21 Aug 2026 19 Nov 2026 ECDSA 256 ECDSA-SHA384 688c4daf5300c51e0a5c1f6837a3a67a868
SANs: *.fly.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of trinity-v2-mcp.fly.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
fly.dev. 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://trinity-v2-mcp.fly.dev/mcp Verified 200
http (plaintext) http://trinity-v2-mcp.fly.dev/mcp HTTPS enforced 301 https://trinity-v2-mcp.fly.dev/mcp
MCP tools · 4 exposed · ~365 tokens

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 →

Tool Tokens
multi_source_validator ~131

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. 'contradicted' is used only when sources actively assert the opposite; absence of evidence yields 'unverified'.

NameTypeReqDescription
claimstringyesThe factual claim to verify against multiple web sources.
countintegerHow many web sources to consult (default 5, max 10).

No output schema declared.

No examples provided.

ping ~38

Liveness probe. Returns 'pong' plus any supplied message.

NameTypeReqDescription
messagestring|nullOptional message echoed back, to verify round-trip serialization.

No output schema declared.

No examples provided.

privacy_shield_redact ~73

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.

NameTypeReqDescription
textstringyesThe text to scan and redact for personally identifiable information.

No output schema declared.

No examples provided.

structured_brief_synthesizer ~123

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.

NameTypeReqDescription
formatstringOutput format: "synthesis" (narrative, default), "summary" (bullets), or "integrated" (shows how sources logically connect).
sourcesarrayyesSources to integrate (each with a title and content).

No output schema declared.

No examples provided.

Common questions

What is the dk.humanified/trinity-research MCP server?

dk.humanified/trinity-research is an MCP server listed in the public MCP registry as dk.humanified/trinity-research. Fact-check claims against live web sources: verdict, consensus, cited sources, PII redaction. This page covers its hosted endpoint (https://trinity-v2-mcp.fly.dev/mcp).

Is the dk.humanified/trinity-research MCP server safe to use?

dk.humanified/trinity-research scores 79 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 dk.humanified/trinity-research MCP server expose?

dk.humanified/trinity-research exposes 4 tools: multi_source_validator, ping, privacy_shield_redact, structured_brief_synthesizer. Their descriptions and schemas cost roughly 365 tokens of context every time the server is loaded.

Does the dk.humanified/trinity-research MCP server require authentication?

No. We connected to dk.humanified/trinity-research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the dk.humanified/trinity-research MCP server still maintained?

dk.humanified/trinity-research is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.