Skip to content
CEO Salary Data from SEC Filings logo

CEO Salary Data from SEC Filings MCP server

Which MCP servers are CEO Salary Data from SEC Filings's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-30

← Back to CEO Salary Data from SEC Filings

Whose server it is
  • Registry nameing.rentseek/evidenceverified in the MCP registry

The registry name sits under rentseek.ing. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-30
  • Stateanswerschecked 2026-10-30
  • Tools2
  • Server calls itselfrentseek-public-facts
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 166 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "Compare two companies' CEO pay packages side by side", the likely first call is get_executive_compensation.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-30
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer209 ms
  • Space in an agent's context≈ 334 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results2 of 2 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Compare two companies' CEO pay packages side by side
  • not sure · Trace a CEO's pay back to its SEC filing
  • not sure · Check CEO pay against shareholder returns over several years

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-30
  • get_executive_compensation

    Returns the latest published annual named-executive compensation rows for a supported company identified by ticker or CIK, including pay components, totals, and filing source URLs. Historical series, pay ratios, pay-versus-performance…

  • list_available_tickers

    Returns ticker symbols for companies with published RentSeek executive-compensation data. Compensation values, evidence lookup, historical data, and purchasing are outside this tool's scope. The result contains availability only, not…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "evidence": {
      "type": "http",
      "url": "https://rentseek.ing/mcp/public-facts"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http rentseek https://rentseek.ing/mcp/public-facts

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://rentseek.ing/mcp/public-facts as a custom connector in the settings.

OpenAPI spec

7 paths, read 2026-10-30. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.