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.

Silicon Friendly

REMOTE · SILICONFRIENDLY.COM

Directory rating websites on AI-agent-friendliness. Search, lookup, and submit.

0 this week 76 Trust /100

Last scanned (20 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 786 tokens (~98/item across 8 items; 8 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 +39
    • Injection markers: unverified → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 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
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.97 ▲ functional
  • 7 Nov 26 −39
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Tool coverage: 100 → unverified ▼ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Oct 26 0
    • Stability: 0.97 → pass security
  • 3 Oct 26 0
    • Stability: pass → 0.97 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 Nov 2026 · Probed https://siliconfriendly.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=siliconfriendly.com CN=YE1,O=Let's Encrypt,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA384 683efcd5167229d5e40c389e22509f79219
SANs: siliconfriendly.com, www.siliconfriendly.com
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 siliconfriendly.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
siliconfriendly.com. No DS 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://siliconfriendly.com/mcp Verified 200
http (plaintext) http://siliconfriendly.com/mcp HTTPS enforced 301 https://siliconfriendly.com/mcp
MCP tools · 8 exposed · ~722 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
check_agent_friendliness ~84

Quick check if a website is in the Silicon Friendly directory and its agent-friendliness level. Args: domain: The website domain to check (e.g. "stripe.com", "github.com") Returns: Simple response with domain, in_directory, level (L0-L5), and whether it's verified.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

get_levels_info ~40

Get info about the 5-level rating system and all 30 criteria. Returns: The level system explanation and all criteria with their descriptions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_verify_queue ~69

Get websites that need verification. Verify them to earn 10 search queries each. Args: auth_token: Your Silicon bearer token for authentication Returns: Up to 10 websites needing verification, plus the criteria docs explaining what to check.

NameTypeReqDescription
auth_tokenstring––

No output schema declared.

No examples provided.

get_website ~74

Get details about a specific website in the Silicon Friendly directory. Args: domain: The website domain (e.g. "stripe.com", "github.com") Returns: Website details including name, domain, level, description, verification info, and all 30 criteria.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

list_verified_websites ~61

List all verified websites in the directory, sorted by most recently updated. Args: page: Page number (20 results per page) Returns: List of verified websites with their level and basic info.

NameTypeReqDescription
pageinteger––

No output schema declared.

No examples provided.

search_websites ~112

Search the Silicon Friendly directory for AI-agent-friendly websites. Args: query: Search terms to find websites (e.g. "payment processing", "email API") search_type: Type of search - 'semantic' (AI-powered, better results) or 'keyword' (exact token match). Default: 'semantic' Returns: List of matching websites with name, domain, level, and similarity/relevance score.

NameTypeReqDescription
querystringyes–
search_typestring––

No output schema declared.

No examples provided.

submit_website ~135

Submit a new website to the Silicon Friendly directory. Requires authentication. Pass your silicon auth_token. Args: url: The website URL (e.g. "https://stripe.com") name: Display name for the website (e.g. "Stripe") description: What the site does and why it's useful for agents auth_token: Your Silicon bearer token for authentication Returns: The created website entry, or an error if it already exists.

NameTypeReqDescription
auth_tokenstring––
descriptionstring––
namestringyes–
urlstringyes–

No output schema declared.

No examples provided.

verify_website ~147

Submit a verification for a website - evaluate it against all 30 criteria. Earns you 10 search queries for each new verification. Args: domain: The website domain to verify (e.g. "stripe.com") criteria: Dict of all 30 boolean criteria fields. See get_verify_queue for field names. Example: {"l1_semantic_html": true, "l1_meta_tags": true, ...} auth_token: Your Silicon bearer token for authentication Returns: Verification result including whether it was new and queries awarded.

NameTypeReqDescription
auth_tokenstring––
criteriaobjectyes–
domainstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Silicon Friendly MCP server?

Silicon Friendly is a hosted endpoint at https://siliconfriendly.com/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 · siliconfriendly.com

# add to Claude Code
claude mcp add --transport http com-siliconfriendly-directory 'https://siliconfriendly.com/mcp'
Common questions

What is the Silicon Friendly MCP server?

Silicon Friendly is an MCP server listed in the public MCP registry as com.siliconfriendly/directory. Directory rating websites on AI-agent-friendliness. Search, lookup, and submit. This page covers its hosted endpoint (https://siliconfriendly.com/mcp).

Is the Silicon Friendly MCP server safe to use?

Silicon Friendly scores 76 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 Silicon Friendly MCP server expose?

Silicon Friendly exposes 8 tools: search_websites, get_website, check_agent_friendliness, submit_website, get_verify_queue, and 3 more. Their descriptions and schemas cost roughly 722 tokens of context every time the server is loaded.

Does the Silicon Friendly MCP server require authentication?

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

Is the Silicon Friendly MCP server still maintained?

Silicon Friendly is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Silicon Friendly MCP server?

VerifyMCP ran 12 checks on Silicon Friendly, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Silicon Friendly: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.