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.

io.github.SiliconRoshiBill/heropedia

REMOTE · WWW.HEROPEDIA.ORG

Consult 324+ expert personas (Buffett, Jobs, Munger, Torvalds, ...) via 4 read-only registry tools.

0 this week 82 Trust /100

Last scanned (4 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 22 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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 284 tokens (~71/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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • 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.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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
  • 6 Nov 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Oct 26 0
    • Stability: 0.93 → pass security
  • 6 Oct 26 0
    • Tool “getDetail” changed its title: Get hero persona cosmetic
    • Tool “getList” changed its title: List heroes cosmetic
    • Tool “getListByHero” changed its title: Find heroes by name cosmetic
    • Tool “getListByRole” changed its title: Find heroes by role cosmetic

    4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 28 Sept 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
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 22 Nov 2026 · Probed https://www.heropedia.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=heropedia.org CN=WE1,O=Google Trust Services,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA256 cb80df66a1d48e65132b005916e3040e
SANs: heropedia.org, www.heropedia.org, *.www.heropedia.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.heropedia.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
heropedia.org. 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://www.heropedia.org/mcp Verified 200
http (plaintext) http://www.heropedia.org/mcp Inconclusive 405
MCP tools · 4 exposed · ~284 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
getDetail ~75

Retrieve the complete canonical Heropedia Role content as raw markdown. Fetch either by unique entry id (preferred after LIST) or by exact hero_name + role_name (when both names are already known). Not a regex tool.

NameTypeReqDescription
hero_namestring––
idstring––
role_namestring––

No output schema declared.

No examples provided.

getList ~54

List Heropedia Hero/Role entries using pagination. Returns lightweight metadata: id, hero_name, role_name, description. Does not return full Role prompts.

NameTypeReqDescription
pageinteger––
page_sizeinteger––

No output schema declared.

No examples provided.

getListByHero ~81

List Heropedia Hero/Role entries whose Hero name matches the supplied regex. Use when you know or can identify the Hero and want to inspect that Hero's available Roles. Regex is case-insensitive; safe subset only. Returns lightweight metadata.

NameTypeReqDescription
hero_regexstringyes–
pageinteger––
page_sizeinteger––

No output schema declared.

No examples provided.

getListByRole ~74

List Heropedia Hero/Role entries whose Role name matches the supplied regex. Use when you want to inspect Heroes offering a particular Role. Regex is case-insensitive; safe subset only. Returns lightweight metadata.

NameTypeReqDescription
pageinteger––
page_sizeinteger––
role_regexstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.SiliconRoshiBill/heropedia MCP server?

io.github.SiliconRoshiBill/heropedia is a hosted endpoint at https://www.heropedia.org/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.heropedia.org

# add to Claude Code
claude mcp add --transport http siliconroshibill-heropedia 'https://www.heropedia.org/mcp'
Common questions

What is the io.github.SiliconRoshiBill/heropedia MCP server?

io.github.SiliconRoshiBill/heropedia is an MCP server listed in the public MCP registry as io.github.SiliconRoshiBill/heropedia. Consult 324+ expert personas (Buffett, Jobs, Munger, Torvalds, ...) via 4 read-only registry tools. This page covers its hosted endpoint (https://www.heropedia.org/mcp).

Is the io.github.SiliconRoshiBill/heropedia MCP server safe to use?

io.github.SiliconRoshiBill/heropedia scores 82 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 io.github.SiliconRoshiBill/heropedia MCP server expose?

io.github.SiliconRoshiBill/heropedia exposes 4 tools: getList, getListByHero, getListByRole, getDetail. Their descriptions and schemas cost roughly 284 tokens of context every time the server is loaded.

Does the io.github.SiliconRoshiBill/heropedia MCP server require authentication?

No. We connected to io.github.SiliconRoshiBill/heropedia without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.SiliconRoshiBill/heropedia MCP server still maintained?

io.github.SiliconRoshiBill/heropedia is still listed as active in the MCP registry. We last reached this channel on 22 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 io.github.SiliconRoshiBill/heropedia MCP server?

VerifyMCP ran 12 checks on io.github.SiliconRoshiBill/heropedia, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.SiliconRoshiBill/heropedia: HTTPS. 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.