Skip to content

MCP servers › work.agentexchange › feeds

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

feeds MCP server

Registry name work.agentexchange/feeds

Paid feeds and pre-payment checks (x402) — the publisher's title

by agentexchange.work · domain (the registry's namespace rule)Website ↗

27 paid feeds from 0.002 USD: OFAC sanctions screen, pre-payment check, token check, SEC, weather. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-19version 1.0.1streamable HTTP28 tools

Summary

work.agentexchange/feeds is a remote MCP server listed in the official MCP registry at version 1.0.1, under the namespace of the domain agentexchange.work. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 28 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
28
Last tested
2026-11-19

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-19 (feeds.agentexchange.work), 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.0.1).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-19
Mode
read-only (no tool calls)
Latest version
1.0.1, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-19 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-11-19; 2 in the 90 days before the 2026-11-19 snapshot.
Most recent 2 versions
  • 1.0.1 · 2026-11-19
  • 1.0.0 · 2026-11-19
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19
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

New in the registry: not in the list of 2026-11-18, listed on 2026-11-19 with version 1.0.1 (published 2026-11-19).

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19.

What it is

What does this server offer?

Observed inventory
28tools
0resources
0prompts

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

  • federal_registeron 6 other servers

    “Newest US Federal Register documents in one call: rules, proposed rules, notices or presidential documents with agencies, publication date, document number, abstract and link (type=RULE|PRORULE|NOTIC…”

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

    3 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • typestring“RULE, PRORULE, NOTICE or PRESDOCU”
    • countstring“up to 50”
  • “Newest US consumer product safety recalls (CPSC) in one call: recall number, date, product names, hazards, remedies, manufacturers, units, link (days=1..30, count up to 50).”

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

    3 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • daysstring“1 to 30”
    • countstring“up to 50”
  • drug_shortageson 1 other server

    “FDA drug shortage records most recently updated (openFDA): generic name, status, presentation, reason, update date, therapeutic category (count up to 50, status=Current|Resolved|To Be Discontinued).”

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

    3 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • statusstring“Current, Resolved or To Be Discontinued”
    • countstring“up to 50”
  • weather_alertson 10 other servers

    “Active US National Weather Service alerts in one call, severe and extreme first: event, severity, area, headline, onset, expires, sender (area=two-letter state, severity=Severe|Extreme|Moderate, coun…”

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

    4 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • areastring“two-letter US state”
    • severitystring“Extreme, Severe, Moderate”
    • countstring“up to 50”
  • cot

    “CFTC Commitments of Traders, latest weekly report in one call: per futures market open interest, non-commercial (speculator) long/short and net, commercial long/short and net; filter market=<name con…”

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

    3 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • marketstring“name contains, e.g.”
    • countstring“up to 50”
  • “Newest EU public procurement notices from TED in one call: notice number, publication date, buyer, notice type, title, link to the notice (days=1..14, country=3-letter code such as DEU or FRA, count …”

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

    4 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • countrystring“3-letter code, e.g.”
    • daysstring“1 to 14”
    • countstring“up to 50”
  • filings_latest

    “Newest SEC EDGAR filings across ALL companies in one call (form=8-K default, also 10-K, 10-Q, 4, S-1, 13F-HR; count 10, 20, 40, 80 or 100): company, CIK, accession, filed time, 8-K items, document in…”

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

    3 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • formstring“8-K (default), 10-K, 10-Q, 4, S-1”
    • countstring“10, 20, 40, 80 or 100”
  • gov_contracts

    “Newest US federal contract awards above an amount in one call (USAspending): recipient, amount, awarding agency, last modified, description, award id (min_amount default 1000000, days 1..7, count up …”

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

    4 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • min_amountstring“USD, default 1000000”
    • daysstring“1 to 7”
    • countstring“up to 50”
  • airport_delayson 2 other servers

    “Current FAA airport delays and closures in one call: ground delay programs, ground stops, arrival/departure delays and closures by airport with reason and duration (airport=3-letter code optional).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • airportstring“3-letter code, e.g.”
  • us_treasury

    “US Treasury fiscal snapshot in one call: total public debt outstanding to the penny (latest and previous day, change), debt held by public and intragovernmental, and the latest average interest rates…”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • daysstring“1 to 30, daily debt series”
  • pypi_packageon 3 other servers

    “Python package facts from PyPI in one call: latest version, summary, required Python, license, project URLs, number of releases, latest upload (name=requests).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • namestring“package name, e.g.”
  • “npm package facts in one call: latest version, description, license, dependency count, repository, weekly downloads (name=express).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • namestring“package name, e.g.”
Show 16 more tools
  • “Is this URL up right now: live HEAD request from the edge following up to 5 redirects: final URL, status, content type, server, redirect chain, latency (url=https://example.com).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • urlstring“public http(s) URL to check”
  • “Public holidays for a country and year in one call: date, name, local name, type (country=US, year=2026).”

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

    3 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • countrystring“2-letter code, default US”
    • yearstring“default current year”
  • “Email address pre-check in one call: syntax, MX records (or A fallback), likely deliverable, known disposable domain (email=a@example.com).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • emailstring“address to check, e.g.”
  • security_headerson 11 other servers

    “HTTP security header audit of a URL in one call: HSTS, CSP, nosniff, frame protection, referrer, permissions and COOP policies, score and A to D grade (url=https://example.com).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • urlstring“public URL to inspect”
  • ai_readinesson 1 other server

    “Is this site ready for AI agents in one call: robots.txt AI-bot rules, llms.txt, agent-card.json, openapi.json, x402 well-known, MCP server card, readiness score (url=https://example.com).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • urlstring“site or origin to check”
  • “Sitemap facts for a site in one call: sitemap location (robots.txt aware), index or urlset, entry count, sample URLs, newest and oldest lastmod (url=https://example.com).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • urlstring“site or origin”
  • “Page metadata in one call: title, description, canonical, language, Open Graph and Twitter card tags, robots meta, h1s, JSON-LD types, link and image counts (url=https://example.com/page).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • urlstring“public page URL”
  • base_token_checkon 4 other servers

    “Base ERC-20 pre-trade check from the chain itself in one call: contract or not, name, symbol, supply, owner and renounced status, upgradeable-proxy slots, mint/blacklist/pause/fee-setter selectors in…”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • tokenstring“Base ERC-20 address, 0x...”
  • weather_forecaston 28 other servers

    “US weather forecast for a point in one call from the National Weather Service: current hour and the next 8 forecast periods with temperature, wind, precipitation chance, short and detailed forecast, …”

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

    3 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • latstring“latitude, e.g.”
    • lonstring“longitude, e.g.”
  • “Domain registration facts in one call from the registry RDAP service: registered or not, status, created, updated and expiry dates, registrar, nameservers, DNSSEC (domain=example.com).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • domainstring“domain name, e.g.”
  • papers_searchon 8 other servers

    “Scholarly paper search in one call from Crossref: DOI, title, authors, year, journal, citation count, link for the best matches (q=topic words, count up to 25, from_year optional).”

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

    4 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • qstring“topic or title words”
    • countstring“1 to 25”
    • from_yearstring“optional, e.g.”
  • “Time zone facts and conversion in one call: local time, UTC offset, abbreviation, whether the zone observes DST and whether it is active, for one IANA zone or two for conversion (zone=Europe/Berlin, …”

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

    4 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • zonestring“IANA zone, e.g.”
    • tostring“optional second zone for conversion”
    • atstring“optional ISO time, default now”
  • isbn_lookup

    “Book facts by ISBN in one call from Open Library: title, subtitle, authors, publishers, publish date, pages, subjects, cover, link (isbn=9780140328721).”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • isbnstring“ISBN-10 or ISBN-13”
  • sanctions_checkon 15 other servers

    “OFAC sanctions screen in one call against the US Treasury SDN list: by name (also matches aliases) or by crypto address (SDN-listed digital currency addresses): matches with entity number, type, prog…”

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

    3 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • namestring“person or company name”
    • addressstring“or a crypto address, 0x...”
  • payment_precheck

    “One call before an agent sends money: screens the recipient address against the OFAC sanctions list, inspects it on Base (contract or wallet, owner, proxy, mint/blacklist/fee flags) and, if a payee d…”

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

    3 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • addressstring“recipient EVM address 0x...”
    • domainstring“optional: the merchant or payee domain, e.g.”
  • seller_benchmark

    “Benchmark one of your own paid x402 routes in one call: whether it is indexed in the Coinbase Bazaar, its 30-day calls and unique payers, its rank among peers for its own description, peer median pri…”

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

    2 inputs
    • x_paymentstring“signed x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements”
    • urlstring“URL of one of your paid x402 routes”

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-19.

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
100% of 75
Tools with a description
100% of 28
Typical description length
290 characters

The tool set

Counted from the listing

Tools
28
Size of the list
about 7,083 tokens for an agent to load (characters ÷ 4)
Naming
24 of 28 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 28 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-19 (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://feeds.agentexchange.work/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "feeds": {
      "url": "https://feeds.agentexchange.work/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "feeds": {
      "type": "http",
      "url": "https://feeds.agentexchange.work/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"feeds","type":"http","url":"https://feeds.agentexchange.work/mcp"}'
Claude Code
claude mcp add --transport http feeds https://feeds.agentexchange.work/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "feeds": {
      "type": "streamableHttp",
      "url": "https://feeds.agentexchange.work/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "feeds": {
      "httpUrl": "https://feeds.agentexchange.work/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.feeds]
url = "https://feeds.agentexchange.work/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "feeds": {
      "url": "https://feeds.agentexchange.work/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://feeds.agentexchange.work/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-19. 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-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

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 feeds.agentexchange.work/mcpSession openedmatchesour test · 2026-11-19
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-19

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-19. 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 work.agentexchange/feeds

Answered from the data above

Who publishes work.agentexchange/feeds?

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

Does work.agentexchange/feeds need an API key or sign-in?

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

Has work.agentexchange/feeds been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its 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). This is our choice, not a block by the server. 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

Not probed (no operator permission)

We connected and read what the server declares, but did not call its 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). This is our choice, not a block by the server. 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-19
  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-19, 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. 192 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 28 tools, 0 resources, 0 prompts.
  4. 991 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-19; 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-19
MCP capability
tools
our test · 2026-11-19
Transport
streamable HTTP
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · 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-19
Lifecycle status
registry · 2026-11-19
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-19

“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. “work.agentexchange/feeds: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/work.agentexchange/feeds

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/work.agentexchange/feeds)](https://protocolprobe.com/mcp/servers/work.agentexchange/feeds)

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