Skip to content
MCPSTAMP
MCP server report

SecFeed MCP server

com.secfeedapi/secfeed

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 71 of 100 (grade C), higher than 11.4% of the 33,003 registry servers that responded over HTTPS that day. Ready for Gemini and MCP Registry. Not ready for Claude and ChatGPT.

Measured facts

Score
71C
Sign-in
No sign-in
Tools listed
40
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by readOnlyHint or destructiveHint on every tool and Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT) and Human-readable title on every tool.
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

6 checks to fix

  1. Fails

    readOnlyHint or destructiveHint on every tool

    tool_annotations

    Blocks Claude and ChatGPT.

    Measured 40/40 tools set neither readOnlyHint nor destructiveHint: search_filings, full_text_search, extract_section, xbrl_to_json, financial_statements and 35 more

    Set annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).

  2. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 40/40 tools miss an explicit hint: search_filings, full_text_search, extract_section, xbrl_to_json, financial_statements and 35 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  3. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 40/40 without title: search_filings, full_text_search, extract_section, xbrl_to_json, financial_statements and 35 more

    Add a short human-readable "title" to every tool (shown in store UIs and consent screens).

  4. Fails

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured Unknown method returned a result

    Return JSON-RPC error -32601 (Method not found) for unknown methods instead of a result.

  5. Fails

    Server instructions

    instructions

    Measured No instructions in the initialize result

    Add an "instructions" string to the initialize result: what the server covers, for whom, and its limits.

  6. Warning

    Tool descriptions

    tool_descriptions

    Measured 13 under 60 chars: company_facts, form_13f_holdings, map_ticker, map_cusip, shares_outstanding and 8 more

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

11 checks passed, 10 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, GET answers SSE or 405, initialize latency, serverInfo name and version, tools capability declared, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable.

Not run. Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. The server asks for no sign-in, so the OAuth checks do not apply.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for SecFeed

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fsecfeedapi.com%2Fmcp)](https://www.mcpstamp.com/r/com-secfeedapi-secfeed/)

HTML

<a href="https://www.mcpstamp.com/r/com-secfeedapi-secfeed/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fsecfeedapi.com%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

SEC EDGAR data as tools: filing search, full text, XBRL financials, insider trades, 13F, 8-K events.
Registry name
com.secfeedapi/secfeed
Remote URL
https://secfeedapi.com/mcp
Version
1.0.0
Website
secfeedapi.com/mcp/
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade C servers

All grade C servers · All server reports · State of MCP readiness, November 2026