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.

RentSeek Evidence

REMOTE · RENTSEEK.ING · 2 COMPONENTS · SCANNED SEP 20

Source-linked executive compensation data for AI agents and developers.

0 this week 91 Trust /100
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 Security94
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 667 tokens (~133/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 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
Install

How do I install the RentSeek Evidence MCP server?

RentSeek Evidence is a hosted endpoint at https://rentseek.ing/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 · rentseek.ing

# add to Claude Code
claude mcp add --transport http ing-rentseek-evidence 'https://rentseek.ing/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ing-rentseek-evidence": {
      "url": "https://rentseek.ing/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ing-rentseek-evidence": {
      "type": "http",
      "url": "https://rentseek.ing/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ing-rentseek-evidence]
url = "https://rentseek.ing/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ing-rentseek-evidence": {
      "type": "remote",
      "url": "https://rentseek.ing/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ing-rentseek-evidence --url 'https://rentseek.ing/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ing-rentseek-evidence:
    url: "https://rentseek.ing/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ing-rentseek-evidence": {
      "Transport": "http",
      "Url": "https://rentseek.ing/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ing-rentseek-evidence -t streamable-http -u 'https://rentseek.ing/mcp'
// mcp.json
{
  "mcpServers": {
    "ing-rentseek-evidence": {
      "type": "http",
      "url": "https://rentseek.ing/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 26 Aug 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
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 11 Aug 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
  • 31 Jul 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
  • 30 Jul 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
  • 27 Jul 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
  • 26 Jul 26 0

    First indexed and scored.

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 20 Sept 2026 · Probed https://rentseek.ing/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rentseek.ing CN=YR1,O=Let's Encrypt,C=US 27 Aug 2026 25 Nov 2026 RSA 2048 SHA256-RSA 5a6a15f9c53fc58a4bc7ac48971a1781e9a
SANs: rentseek.ing
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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 rentseek.ing. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ing. present 27256 8 Verified
rentseek.ing. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://rentseek.ing/.well-known/oauth-protected-resource" scope="executive-compensation:read"

Bearer resource_metadata="https://rentseek.ing/.well-known/oauth-protected-resource" scope="executive-compensation:read"
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://va.vercel-scripts.com https://browser.sentry-cdn.com https://t.rentseek.ing https://us-assets.i.posthog.com https://www.googletagmanager.com https://connect.facebook.net https://googleads.g.doubleclick.net; style-src 'self' 'unsafe-inline' https://us.posthog.com; img-src 'self' data: https: https://www.facebook.com; font-src 'self' data:; connect-src 'self' https://api.openai.com https://data.sec.gov https://www.sec.gov https://*.blob.vercel-storage.com https://blob.vercel-storage.com https://*.sentry.io https://*.ingest.sentry.io https://va.vercel-scripts.com https://vitals.vercel-insights.com https://t.rentseek.ing https://us.posthog.com https://us-assets.i.posthog.com https://internal-j.posthog.com https://www.google-analytics.com https://www.googletagmanager.com https://www.facebook.com https://googleads.g.doubleclick.net https://ad.doubleclick.net https://pagead2.googlesyndication.com https://www.googleadservices.com https://www.google.com htt
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Protected resource metadata

Document https://rentseek.ing/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://rentseek.ing/mcp
Authorisation server https://rentseek.ing

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://rentseek.ing/mcp Verified 200
http (plaintext) http://rentseek.ing/mcp HTTPS enforced 308 https://rentseek.ing/mcp
MCP tools · 5 exposed · ~667 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
get_claim_evidence ~74

Returns the value, filing source, release identity, methodology version, and current or superseded status for a RentSeek `clm_...` claim ID. Requires OAuth or X-API-KEY and costs 1 credit. The result is filing evidence, not investment advice.

NameTypeReqDescription
claim_idstringyes

No output schema declared.

No examples provided.

get_company_dossier ~94

Returns a sourced company dossier for a ticker, including executives, compensation history, pay ratio, pay-versus-performance, claims, and release provenance, with optional full or compact format and field projection. Requires OAuth or X-API-KEY and costs 3 credits. The result is filing evidence, not investment advice.

NameTypeReqDescription
fieldsarray
formatstring
tickerstringyes

No output schema declared.

No examples provided.

get_executive_compensation ~217

Returns annual named-executive compensation rows for a company identified by ticker or CIK, with fiscal-year filters, pay components, totals, and filing source URLs. Latest-FY requests cost 0 credits; historical, range, or multi-FY requests require OAuth or X-API-KEY and cost 1 credit. Pay ratio, pay-versus-performance, and company dossiers are not included. The result is filing data, not investment advice.

NameTypeReqDescription
cikstring
fiscal_yearintegerExact fiscal year. Omit all fiscal-year filters to get the latest year.
fiscal_year_gteintegerInclusive earliest fiscal year. Omit all fiscal-year filters to get the latest year.
fiscal_year_lteintegerInclusive latest fiscal year. Omit all fiscal-year filters to get the latest year.
limitintegerMaximum fiscal years to return. Defaults to the latest year only.
periodstring
tickerstring

No output schema declared.

No examples provided.

list_available_tickers ~53

Returns ticker symbols for companies with published RentSeek executive-compensation data. No authentication is required, and the request costs 0 credits. The result contains availability only, not compensation values. It is not investment advice.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_material_changes ~229

Returns classified executive-compensation disclosure changes for 1-50 tickers since an inclusive date or timestamp, with configurable thresholds and cursor pagination. Requires OAuth or X-API-KEY and costs 2 credits per page. Current compensation snapshots and full historical rows are not included. The result is filing evidence, not investment advice.

NameTypeReqDescription
classificationstringEvent classification to return. Omit to return material events only; use all to include informational events.
cursorstringOpaque next_cursor from a prior response. Omit for the first page.
page_sizeintegerEvents per page. Omit to use 25; maximum 100.
sincestringyesInclusive ISO date or timestamp from the caller's prior feed run.
threshold_component_pctnumberMaterial compensation-component change percent. Omit to use 30%.
threshold_total_pctnumberMaterial total-compensation change percent. Omit to use 20%.
tickersarrayyesTicker symbols to monitor. Pass 1-50 symbols in one request.

No output schema declared.

No examples provided.

Common questions

What is the RentSeek Evidence MCP server?

RentSeek Evidence is an MCP server listed in the public MCP registry as ing.rentseek/evidence. Source-linked executive compensation data for AI agents and developers. This page covers its hosted endpoint (https://rentseek.ing/mcp).

Is the RentSeek Evidence MCP server safe to use?

RentSeek Evidence scores 91 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 RentSeek Evidence MCP server expose?

RentSeek Evidence exposes 5 tools: get_executive_compensation, get_company_dossier, get_claim_evidence, list_material_changes, list_available_tickers. Their descriptions and schemas cost roughly 667 tokens of context every time the server is loaded.

Does the RentSeek Evidence MCP server require authentication?

Yes. RentSeek Evidence asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the RentSeek Evidence MCP server still maintained?

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