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.

Circuit

REMOTE · WWW.CIRCUIT.FAMILY

Find and try paid AI agent skills for security, on-chain data, code, markets, research and news.

+3 this week 84 Trust /100

Last scanned (22 hours ago)

Scores higher than 89% of remote servers

Reachable. Last reached 4 Nov 2026.

Category AI and Machine Learning

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 Security80
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 443 tokens (~110/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 Management83
  • Stability observed for 25 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
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
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 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 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.

  • 27 Oct 26 +1

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

  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

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 4 Nov 2026 · Probed https://www.circuit.family/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.circuit.family CN=YR2,O=Let's Encrypt,C=US 10 Oct 2026 8 Jan 2027 RSA 2048 SHA256-RSA 67df81d926440e47dc21071c28ad7be861f
SANs: *.circuit.family, circuit.family
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.circuit.family. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
family. present 30022, 51152 8, 8 Verified
circuit.family. 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
Header Value
strict-transport-security max-age=63072000
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.circuit.family/mcp Verified 200
http (plaintext) http://www.circuit.family/mcp HTTPS enforced 308 https://www.circuit.family/mcp
MCP tools · 4 exposed · ~322 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
find_skills ~143

Search Circuit's paid AI agent skills by capability, e.g. 'phishing link', 'token price' or 'summarize a web page'. Returns each skill's id, price in USDG, summary and 30-day usage. Free.

NameTypeReqDescription
categorystring–Optional category, e.g. Security, On-chain, Developer, Market Data, Research, News.
limitinteger–Most results to return (default 10).
maxPricenumber–Optional highest price per call in USDG, e.g. 0.005.
querystring–What the skill should do. Leave empty to list everything.

No output schema declared.

No examples provided.

get_skill ~66

Full details for one skill: input and output schema, a real example, price, 30-day usage, uptime, rating and how to pay for it. Free.

NameTypeReqDescription
skill_idstringyesSkill id from find_skills, e.g. 'bastion/url-risk'.

No output schema declared.

No examples provided.

list_recipes ~41

Workflows that chain several skills (vet a token, install a dependency safely, screen untrusted input and more), with the cost of one run. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

try_skill ~72

Run a skill once for free on a small input (text up to 500 characters). 3 free calls per day. Paid calls have no such limits.

NameTypeReqDescription
inputobjectyesInput matching the skill's input schema.
skill_idstringyesSkill id, e.g. 'ticker/token-price'.

No output schema declared.

No examples provided.

Install

How do I install the Circuit MCP server?

Circuit is a hosted endpoint at https://www.circuit.family/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 · www.circuit.family

# add to Claude Code
claude mcp add --transport http family-circuit-marketplace 'https://www.circuit.family/mcp'
Common questions

What is the Circuit MCP server?

Circuit is an MCP server listed in the public MCP registry as family.circuit/marketplace. Find and try paid AI agent skills for security, on-chain data, code, markets, research and news. This page covers its hosted endpoint (https://www.circuit.family/mcp).

Is the Circuit MCP server safe to use?

Circuit 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 Circuit MCP server expose?

Circuit exposes 4 tools: find_skills, get_skill, try_skill, list_recipes. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.

Does the Circuit MCP server require authentication?

No. We connected to Circuit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Circuit MCP server still maintained?

Circuit 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.