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.

SiteCheck Agent Intel & Dev

REMOTE · API.FADEANDCO.WORKERS.DEV

135 pay-per-call agent tools: agent intelligence, token risk, developer and AI data tools. x402

66 Trust /100

Last scanned (2 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Crypto and Web3

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 Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 21425 tokens (~158/item across 135 items; 135 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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 135 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 136 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
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.

  • 24 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “agent_intel_invoice_document_ocr” rewrote its description, which is the text the model reads security
    • Tool “agent_intel_speech_to_text_transcribe_turbo” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • “agent_intel_invoice_document_ocr” added an optional parameter “imageUrl” cosmetic
    • “agent_intel_speech_to_text_transcribe_turbo” added an optional parameter “audioUrl” cosmetic
    • “agent_intel_invoice_document_ocr” reworded the description of “imageBase64” cosmetic
    • “agent_intel_invoice_document_ocr” reworded the description of “mime” cosmetic
    • “agent_intel_speech_to_text_transcribe_turbo” reworded the description of “audioBase64” cosmetic
    • “agent_intel_invoice_document_ocr” made “imageBase64” optional cosmetic
    • “agent_intel_speech_to_text_transcribe_turbo” made “audioBase64” optional cosmetic
  • 23 Oct 26 65

    First indexed and scored.

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 24 Oct 2026 · Probed https://api.fadeandco.workers.dev/mcp?ref=registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fadeandco.workers.dev CN=YE1,O=Let's Encrypt,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA384 6333e519a4cacb6a887e102975c050b4fca
SANs: *.fadeandco.workers.dev, fadeandco.workers.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 api.fadeandco.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.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://api.fadeandco.workers.dev/mcp?ref=registry Verified 200
http (plaintext) http://api.fadeandco.workers.dev/mcp?ref=registry Served over HTTP 200
MCP tools · 135 exposed · ~21,286 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
dev_youtube_channel ~117

YouTube channel public details by @handle from the channel page: channel id, name, description (YouTube truncates it), subscriber count as YouTube rounds it (e.g. 44.7 million) and exact video count. Public page data; English locale; no per-video stats. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

NameTypeReqDescription
handlestringyesChannel handle without @, e.g. TED
NameTypeReqDescription
channelId–––
checkedAt–––
description–––
handle–––
name–––
source–––
subscribersText–––
videoCount–––

No examples provided.

Install

How do I install the SiteCheck Agent Intel & Dev MCP server?

SiteCheck Agent Intel & Dev is a hosted endpoint at https://api.fadeandco.workers.dev/mcp?ref=registry, 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 · api.fadeandco.workers.dev

# add to Claude Code
claude mcp add --transport http bck-stack-sitecheck-agent-intel-dev 'https://api.fadeandco.workers.dev/mcp?ref=registry'
Common questions

What is the SiteCheck Agent Intel & Dev MCP server?

SiteCheck Agent Intel & Dev is an MCP server listed in the public MCP registry as io.github.bck-stack/sitecheck-agent-intel-dev. 135 pay-per-call agent tools: agent intelligence, token risk, developer and AI data tools. x402. This page covers its hosted endpoint (https://api.fadeandco.workers.dev/mcp?ref=registry).

Is the SiteCheck Agent Intel & Dev MCP server safe to use?

SiteCheck Agent Intel & Dev scores 66 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 SiteCheck Agent Intel & Dev MCP server expose?

SiteCheck Agent Intel & Dev exposes 135 tools: agent_intel_deep_research, agent_intel_web_search_turbo, agent_intel_news_radar, agent_intel_social_signal_aggregator, agent_intel_reader_markdown_extract, and 130 more. Their descriptions and schemas cost roughly 21,286 tokens of context every time the server is loaded.

Does the SiteCheck Agent Intel & Dev MCP server require authentication?

No. We connected to SiteCheck Agent Intel & Dev without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SiteCheck Agent Intel & Dev MCP server still maintained?

SiteCheck Agent Intel & Dev is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.