Skip to content

MCP servers › com.seraphixsystems › public-records

MCP server · registry snapshot 2026-11-14 · last tested 2026-11-14

public-records MCP server

Registry name com.seraphixsystems/public-records

Seraphix Public Records — the publisher's title

by seraphixsystems.com · domain (the registry's namespace rule)Website ↗

Source-linked public records on any US organization: SEC, IRS 990, federal awards, banks, lobbying. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-14version 1.1.0streamable HTTP20 tools

Summary

com.seraphixsystems/public-records is a remote MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain seraphixsystems.com. On 2026-11-14 ProtocolProbe connected to it in read-only mode and read its inventory: 20 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
20
Last tested
2026-11-14

Tool list size

7,466 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (20 tools). Counted with Anthropic's token counter on 2026-11-14, from the tool list we read on 2026-11-14. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-14 (seraphixsystems.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.1.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (create_board). That is our reading of the names; we did not call it. Source: our connection, 2026-11-14.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-14
Mode
read-only (no tool calls)
Latest version
1.1.0, published 2026-11-13 (registry, as of the 2026-11-14 snapshot)
First listed version
2026-11-06 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-11-06 to 2026-11-13; 2 in the 90 days before the 2026-11-14 snapshot.
Most recent 2 versions
  • 1.1.0 · 2026-11-13
  • 1.0.0 · 2026-11-06
(versions still listed in the registry only)
Registry data
snapshot 2026-11-14
Package and repository
checked 2026-11-14
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.0 (published 2026-11-06) → 1.1.0 (published 2026-11-13), between the registry lists of 2026-11-13 and 2026-11-14.

No release note: the registry entry links no GitHub repository.

Source: the official MCP Registry list on 2026-11-13 and on 2026-11-14; release notes from the GitHub Releases API, checked 2026-11-14.

What it is

What does this server offer?

Observed inventory
20tools
0resources
0prompts

None of its 20 tools are described as changing anything. For 20 the reading was uncertain, so no mark is shown.

  • search_recordson 29 other servers

    “Search Seraphix public records: dated, source-linked statements taken from primary documents (SEC filings, statutes, official codes) about the companies Seraphix covers and state data-center policy.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • querystring“Words to match, e.g.”
    • companystring“Restrict to one covered company: name, former name, SEC CIK or slug (see list_companies).”
    • typestring“Record section: sites, power, incentives, water_permits or policy.”
    • sincestring“Only records whose record_date is on or after this ISO 8601 date, e.g.”
    • limitinteger“Maximum results (1-50, default 10).”
    • tierstring“"reviewed" (default) or "all" to include unreviewed records.”
  • “Fetch one Seraphix public record by ID, with everything needed to cite and check it: the claim, the verbatim quote, source_url, source title, publisher and locator, source_date, published_at, the pri…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Record ID, e.g.”
  • list_companieson 41 other servers

    “List every company in the Seraphix dossier index (the only companies Seraphix covers), alphabetically, with SEC CIK, role, dossier status (FULL = reviewed sections on file; STUB = identity and SEC fi…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Get one covered company by name, former name, SEC CIK or slug: identity (legal name, former names, state of incorporation, SEC EDGAR source), dossier status, a plain-language coverage statement sayin…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • name_or_idstringrequired“Company name, former name, SEC CIK (leading zeros optional) or slug, e.g.”
  • get_filings_wire

    “List SEC EDGAR filings accepted for the companies Seraphix covers, newest first: company, CIK, form, 8-K item codes and titles, SEC acceptance time (source_date), accession number and the SEC filing …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • sincestring“Only filings accepted on or after this ISO 8601 date or date-time, e.g.”
    • companystring“Restrict to one covered company: name, SEC CIK or slug.”
    • limitinteger“Maximum notices (1-100, default 25).”
  • “Describe exactly what Seraphix covers and what it does not, from the published data: companies tracked and their dossier status, states, record counts by tier, each source with its status (OBSERVED, …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Start here with a plain-language question, e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • questionstringrequired“The question, in plain words.”
    • limitinteger“Maximum records (1-20, default 5).”
  • graph_neighborhood

    “Return the part of the Seraphix graph around one node: the companies, corporate parents and subsidiaries, data-center sites, states, records and SEC filings linked to it, up to depth 3 (at most 200 n…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • nodestringrequired“Company name, SEC CIK, or a node id such as place:TX or rec:SX-07-A-0001.”
    • depthinteger“How many links out from the node (1-3, default 1).”
  • who_is_behind

    “Resolve a company, subsidiary or site name to its corporate chain: the matched entity, each parent up to the top parent (with the source and date of each link), the sites it operates, and how many Se…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • namestringrequired“A company, subsidiary or site name, or an SEC CIK.”
  • “Build a graph board from up to 10 seed nodes (each expanded to depth 1 or 2) plus up to 50 notes you add, store it, and return a url a person can open on seraphixsystems.com to explore and keep editi…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    4 inputs, 1 required
    • titlestring“Board title shown to the person.”
    • seedsarrayrequired“Up to 10 company names, SEC CIKs or node ids to start from.”
    • depthinteger“How far to expand each seed (1-2, default 1).”
    • notesarray“Notes to add: each has a label, text, optional https url, the node it is about (attach_to), a link label and its source.”
  • pilot02_follow_the_money

    “For one AI or robotics company, return how it is linked to federal identifiers (each USAspending UEI and LDA client with the basis of the link) and its records: federal contract awards from USAspendi…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • companystring“Company name or slug, e.g.”
    • typestring“Only one record type.”
    • limitinteger
    • offsetinteger
  • tx_site_status

    “For tracked Texas data-center sites, return each milestone (permit, interconnection, energized) with its status, date, source link, the verbatim quote or registry field, and how the source is linked …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • sitestring“Site slug, e.g.”
    • record_idstring“A Seraphix record id, e.g.”
Show 8 more tools
  • search_organizationson 11 other servers

    “Search public sources for an organization by name, ticker, SEC CIK or EIN: public sources (SEC EDGAR (incl.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • qstringrequired“Organization name, ticker, SEC CIK or EIN.”
  • get_organization_record

    “Build (or return the cached, under 24 h) record for one organization id from search_organizations, e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • idstringrequired“Record id, e.g.”
  • screen_organizations

    “Screen up to 25 organization names (500 with a Seraphix API key) against OFAC SDN, SAM.gov exclusions, HHS-OIG LEIE and FARA registrants.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • rowsarrayrequired
  • get_whats_moving

    “Ranked list of organizations whose public record is moving now (new SEC filings, contract awards, lobbying reports, Seraphix records) relative to their usual pace, plus attention on Seraphix.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • categorystring
    • windowstring
  • list_feed_sources

    “List every Seraphix Feed source with its status at this moment (LIVE or DEGRADED, with reasons), last run, window, freshness limit, primary-document domains and item count; the eight free government …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_feed_eventson 2 other servers

    “List feed items, newest first, from LIVE sources only: SEC filings-wire index metadata (filed and accepted times as SEC lists them) and agency records (publication_date, event_date, fetched_at as sto…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • companystring“A tracked company: SEC CIK (leading zeros optional) or slug, e.g.”
    • sourcestring“A source id from list_feed_sources, e.g.”
    • sincestring“ISO 8601 date or date-time.”
    • untilstring“ISO 8601 date or date-time (inclusive).”
    • limitinteger“Maximum items (1-500, default 50).”
    • cursorstring“next_cursor from a previous call, to continue the same query.”
  • what_changed_sinceon 5 other servers

    “For one tracked company, every new item from LIVE sources with its source time on or after `since`, newest first, counted by source, plus the sources that were not LIVE (not checked: no change from t…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 2 required
    • companystringrequired“A tracked company: SEC CIK (leading zeros optional) or slug, e.g.”
    • sincestringrequired“ISO 8601 date or date-time.”
    • limitinteger“Maximum items (1-500, default 50).”
    • cursorstring“next_cursor from a previous call, to continue the same query.”
  • explain_record

    “Return one feed item by id (SX-EW-###### for agency records, SEC-WIRE-<accession> for filings-wire items): the stored record unchanged, its primary document link, the listing link, the stored quote a…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Feed item id, e.g.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-14.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
88% of 42
Tools with a description
100% of 20
Typical description length
532 characters

The tool set

Counted from the listing

Tools
20
Size of the list
about 14,898 tokens for an agent to load (characters ÷ 4)
Naming
19 of 20 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 20 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-14 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://seraphixsystems.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "public-records": {
      "url": "https://seraphixsystems.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "public-records": {
      "type": "http",
      "url": "https://seraphixsystems.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"public-records","type":"http","url":"https://seraphixsystems.com/mcp"}'
Claude Code
claude mcp add --transport http public-records https://seraphixsystems.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "public-records": {
      "type": "streamableHttp",
      "url": "https://seraphixsystems.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "public-records": {
      "httpUrl": "https://seraphixsystems.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.public-records]
url = "https://seraphixsystems.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "public-records": {
      "url": "https://seraphixsystems.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://seraphixsystems.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-14. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-14. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-14. Source: read 2026-11-14.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-14. Source: read 2026-11-14.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint seraphixsystems.com/mcpSession openedmatchesour test · 2026-11-14
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-14

Tool list changes

Our reads compared · no tool called

Hosted endpoint seraphixsystems.com/mcp

1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-07 to 2026-11-14; versions 1.0.0 to 1.1.0).

Last change seen between our reads on 2026-11-07 (version 1.0.0) and 2026-11-14 (version 1.1.0).

Added (14):

answercreate_boardexplain_recordget_feed_eventsget_organization_recordget_whats_movinggraph_neighborhoodlist_feed_sourcespilot02_follow_the_moneyscreen_organizationssearch_organizationstx_site_statuswhat_changed_sincewho_is_behind

Changed (2):

get_record: descriptionsearch_records: description

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-14 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-14. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.seraphixsystems/public-records

Answered from the data above

Who publishes com.seraphixsystems/public-records?

The registry ties the namespace com.seraphixsystems to the domain seraphixsystems.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does com.seraphixsystems/public-records need an API key or sign-in?

It opened a session without any credential on 2026-11-14. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.seraphixsystems/public-records been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-14
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-14, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,448 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 20 tools, 0 resources, 0 prompts.
  4. 5,908 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-14; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-14
MCP capability
tools
our test · 2026-11-14
Transport
streamable HTTP
registry · 2026-11-14
Required credentials
none declared
registry · 2026-11-14 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-14
Lifecycle status
registry · 2026-11-14
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-14

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.seraphixsystems/public-records: MCP server record.” Data checked 2026-11-14. https://protocolprobe.com/mcp/servers/com.seraphixsystems/public-records

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.seraphixsystems/public-records)](https://protocolprobe.com/mcp/servers/com.seraphixsystems/public-records)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology