MCP servers › com.agentdataapi › agentdata
MCP server · registry snapshot 2026-11-14 · last tested 2026-11-14
agentdata MCP server
Registry name com.agentdataapi/agentdata
AgentDataAPI — the publisher's title
by agentdataapi.com · domain (the registry's namespace rule)Website ↗
Grid power prices and carbon, open sensors, weather alerts and forecasts, news and social signals. — the publisher's description
Summary
com.agentdataapi/agentdata is a remote MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain agentdataapi.com. On 2026-11-14 ProtocolProbe connected to it in read-only mode and read its inventory: 41 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
- 41
- Last tested
- 2026-11-14
Tool list size
10,072 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (41 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 (agentdataapi.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).
Observed fact
This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (create_free_api_key). 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-14 (registry, as of the 2026-11-14 snapshot)
- First listed version
- 2026-11-11 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, 2026-11-11 to 2026-11-14; 2 in the 90 days before the 2026-11-14 snapshot.(versions still listed in the registry only)
Most recent 2 versions
1.1.0· 2026-11-141.0.0· 2026-11-11
- 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-11) → 1.1.0 (published 2026-11-14), 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 inventoryNone of its 41 tools are described as changing anything. For 41 the reading was uncertain, so no mark is shown.
- list_capabilitieson 121 other servers
“What this server offers across energy, sensors, weather, news and social: endpoints, prices and the first calls to make.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
- create_free_api_keyon 2 other servers
“Create a FREE AgentDataAPI key (no signup) valid for every slice.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
emailstringrequired“Your human's real email, else your own agent mailbox.”
- grid_regions
“Every power market region we serve: code, market, timezone, currency, source and price cadence.”
Publisher declares: read-only yes · open-world no
1 input
marketstring or null“nem, gb, eu or us; omit for all”
- grid_price
“Latest settled wholesale electricity price for a region (micro units of local currency, USD conversion, demand, negative-price flag).”
Publisher declares: read-only yes · open-world no
2 inputs, 2 required
marketstringrequired“nem (Australia), gb, eu or us”regionstringrequired“Region code, e.g.”
- grid_day_ahead
“Day-ahead (EU) or pre-dispatch (NEM) prices per interval for a local day, with min, max, average and negative intervals.”
Publisher declares: read-only yes · open-world no
3 inputs, 2 required
marketstringrequired“nem (Australia), gb, eu or us”regionstringrequired“Region code, e.g.”datestring or null“Local calendar day YYYY-MM-DD, default tomorrow”
- grid_price_history
“Settled prices for the last 7 days (Pro), optionally averaged per 30 or 60 minutes.”
Publisher declares: read-only yes · open-world no
5 inputs, 2 required
marketstringrequired“nem (Australia), gb, eu or us”regionstringrequired“Region code, e.g.”intervalstring“native, 30m or 60m”fromstring or null“ISO UTC start, default 7 days ago”tostring or null“ISO UTC end, default now”
- grid_loadon 1 other server
“Latest grid demand for a region in MW.”
Publisher declares: read-only yes · open-world no
2 inputs, 2 required
marketstringrequired“nem (Australia), gb, eu or us”regionstringrequired“Region code, e.g.”
- grid_generation
“Latest generation mix for a region: MW per fuel, total and renewables share (basis points).”
Publisher declares: read-only yes · open-world no
2 inputs, 2 required
marketstringrequired“nem (Australia), gb, eu or us”regionstringrequired“Region code, e.g.”
- grid_cheapest_window
“Cheapest contiguous window of N hours in the next horizon from day-ahead or pre-dispatch prices (GB: greenest window from the carbon forecast).”
Publisher declares: read-only yes · open-world no
4 inputs, 2 required
marketstringrequired“nem (Australia), gb, eu or us”regionstringrequired“Region code, e.g.”hoursinteger“Window length in hours”horizoninteger“Look-ahead in hours”
- grid_carbonon 1 other server
“GB grid carbon intensity in gCO2/kWh: actual and forecast now, the next 6 hours, and the regional generation mix.”
Publisher declares: read-only yes · open-world no
1 input
regionstring“GB for national, or a NESO region id 1 to 17 (13 = London)”
- petroleum_weekly
“Latest EIA weekly US petroleum inventory figure with the previous week and the change.”
Publisher declares: read-only yes · open-world no
1 input
seriesstring“crude_stocks, gasoline_stocks, distillate_stocks, refinery_inputs or crude_imports”
- sensors_stations_near
“Stations of every open sensor network near a point, nearest first, with distance and parameters.”
Publisher declares: read-only yes · open-world no
5 inputs, 2 required
latnumberrequired“Latitude in decimal degrees, e.g.”lonnumberrequired“Longitude in decimal degrees, e.g.”radius_kmnumber“Search radius in km, default 25, max 500”parameterstring or null“pm25, pm10, o3, no2, so2, co, gage_height, discharge, water_temp, water_level”networkstring or null“usgs, coops or openaq”
Show 29 more tools
- sensors_air
“Latest air quality readings and US EPA AQI at one monitor.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
station_idstringrequired“openaq_{location_id}, e.g.”
- sensors_air_near
“Air quality monitors near a point with latest readings (PM2.5, PM10, O3, NO2, SO2, CO) and AQI, nearest first.”
Publisher declares: read-only yes · open-world no
3 inputs, 2 required
latnumberrequired“Latitude in decimal degrees, e.g.”lonnumberrequired“Longitude in decimal degrees, e.g.”radius_kmnumber“Search radius in km, default 25, max 500”
- sensors_water_gauge
“Latest river gauge height, discharge and water temperature at a USGS site, with NWS flood stage status.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
sitestringrequired“USGS site number, e.g.”
- sensors_water_history
“Gauge readings for the last 7 days at a USGS site, newest first (Pro).”
Publisher declares: read-only yes · open-world no
4 inputs, 1 required
sitestringrequired“USGS site number, e.g.”startstring or null“ISO time, earliest”endstring or null“ISO time, latest”limitinteger“Max readings to return, default 500”
- sensors_tides
“Latest observed water level (metres MLLW) at a NOAA tide station with the next high and low.”
Publisher declares: read-only yes · open-world no
1 input, 1 required
stationstringrequired“NOAA CO-OPS station id, e.g.”
- sensors_tide_predictions
“Predicted high and low tides for a day at a NOAA tide station.”
Publisher declares: read-only yes · open-world no
2 inputs, 1 required
stationstringrequired“NOAA CO-OPS station id, e.g.”datestring or null“YYYY-MM-DD (UTC), default today”
- sensors_quakes
“Earthquakes in the last N hours from USGS, optionally above a magnitude and within a radius of a point.”
Publisher declares: read-only yes · open-world no
5 inputs
min_magnumber or null“Minimum magnitude, e.g.”hoursinteger“Look-back window in hours, default 24, max 720”latnumber or null“Centre latitude in decimal degrees; with lon and radius_km limits results to a circle”lonnumber or null“Centre longitude in decimal degrees”radius_kmnumber or null“Radius in km around lat/lon, max 20000”
- weather_alertson 10 other servers
“Active weather alerts for a region, severity first.”
Publisher declares: read-only yes · open-world no
3 inputs, 1 required
regionstringrequired“US state (TX), NWS zone or county code (TXZ229), Australian state (NSW), or US / AU”severitystring or null“Extreme, Severe, Moderate, Minor or Unknown”limitinteger“Max alerts to return, default 100”
- weather_currenton 5 other servers
“Current conditions at the nearest reporting station (within 150 km) in the United States or Australia.”
Publisher declares: read-only yes · open-world no
2 inputs, 2 required
latnumberrequired“Latitude, e.g.”lonnumberrequired“Longitude, e.g.”
- weather_forecaston 28 other servers
“Hourly GFS forecast (temperature, humidity, wind, gust, precipitation, cloud) for a point in the contiguous US or Australia.”
Publisher declares: read-only yes · open-world no
3 inputs, 2 required
latnumberrequired“Latitude in decimal degrees, e.g.”lonnumberrequired“Longitude in decimal degrees, e.g.”hoursinteger“Forecast horizon in hours, default 48, max 120”
- weather_forecast_daily
“Daily forecast summary (min and max temperature, wind, gust, precipitation total) for a point in the contiguous US or Australia.”
Publisher declares: read-only yes · open-world no
3 inputs, 2 required
latnumberrequired“Latitude in decimal degrees, e.g.”lonnumberrequired“Longitude in decimal degrees, e.g.”daysinteger“Number of days, default 3, max 5”
- weather_stations_near
“Reporting stations near a point in the United States or Australia, nearest first.”
Publisher declares: read-only yes · open-world no
3 inputs, 2 required
latnumberrequired“Latitude in decimal degrees, e.g.”lonnumberrequired“Longitude in decimal degrees, e.g.”radius_kmnumber“Search radius in km, default 50, max 500”
- news_search_entities
“Search the tracked entities (organisations, tickers, crypto assets, central banks, governments, topics) and get their ids.”
Publisher declares: read-only yes · open-world no
2 inputs
querystring or null“Free text: 'nvidia', 'fed', 'bitcoin'”kindstring or null“org, ticker, crypto, central_bank, government, topic”
- news_sentimenton 2 other servers
“News tone (bps), mentions against the 30-day baseline, volume ratio, novelty and top themes for one entity.”
Publisher declares: read-only yes · open-world no
2 inputs, 1 required
entitystringrequired“Entity id such as org_nvidia, cb_federal_reserve, asset_bitcoin”windowstring“1h, 24h or 7d”
- news_ticker_score
“News score for a ticker: how unusual the coverage volume is and how its tone compares with normal.”
Publisher declares: read-only yes · open-world no
2 inputs, 1 required
symbolstringrequired“Ticker or crypto symbol: NVDA, JPM, BTC”windowstring“1h, 24h or 7d”
- news_trendingon 1 other server
“Entities with the most unusual news volume in the window, ranked by novelty against their baseline.”
Publisher declares: read-only yes · open-world no
3 inputs
kindstring or null“ticker, crypto, org, central_bank, government, topic”windowstring“1h, 24h or 7d”limitinteger“Max entities to return, default 20”
- news_sentiment_history
“Mentions and tone per window or per day for an entity (Pro), newest first.”
Publisher declares: read-only yes · open-world no
3 inputs, 1 required
entitystringrequired“Entity id such as org_nvidia, cb_federal_reserve, asset_bitcoin”intervalstring“15m or 1d”limitinteger“Max points to return, default 60”
- news_trending_people
“Public figures with the biggest attention spike (Wikipedia pageviews and news coverage over their 30-day baseline), by category.”
Publisher declares: read-only yes · open-world no
2 inputs
categorystring or null“celebrity, politics, sport, business, other”limitinteger“Max people to return, default 20”
- news_trending_topics
“Trending topics for a region: top daily searches with headlines, trending Mastodon tags and shared links.”
Publisher declares: read-only yes · open-world no
2 inputs
regionstring“US, AU or GB”limitinteger“Max topics to return, default 20”
- news_top_stories
“The most-covered stories in the window (title, link, publisher, tone), never article text.”
Publisher declares: read-only yes · open-world no
3 inputs
windowstring“1h, 6h or 24h”entitystring or null“Only stories naming this entity id”limitinteger“Max stories to return, default 20”
- social_trending_topics
“Trending hashtags across Bluesky, Mastodon and Nostr (mentions x spike against each tag's baseline), plus Bluesky's own trends list.”
Publisher declares: read-only yes · open-world no
3 inputs
networkstring“all, bluesky, mastodon or nostr”windowstring“1h, 6h or 24h”limitinteger“Max tags to return, default 25”
- social_topic_trend
“One hashtag across networks: mentions per network, expected count, spike, trend, first seen and the last 24 hours by hour.”
Publisher declares: read-only yes · open-world no
2 inputs, 1 required
tagstringrequired“A hashtag without #: 'bitcoin', 'ai', 'f1'”windowstring“1h, 6h or 24h”
- social_trending_links
“The most-shared URLs across networks with titles, shares per network and the Hacker News, Lobsters or Lemmy discussions about them.”
Publisher declares: read-only yes · open-world no
3 inputs
windowstring“1h, 6h or 24h”domainstring or null“Only this domain, e.g.”limitinteger“Max links to return, default 25”
- social_top_mentions
“Stocks and crypto assets ranked by social attention: mentions against a 30-day baseline, spike, lexicon tone, discussions.”
Publisher declares: read-only yes · open-world no
3 inputs
typestring“all, crypto or stock”windowstring“1h, 6h or 24h”limitinteger“Max symbols to return, default 20”
- social_symbol_mentions
“Social volume and tone for one ticker or coin: mentions per network against its baseline, spike, trend and discussions naming it.”
Publisher declares: read-only yes · open-world no
2 inputs, 1 required
symbolstringrequired“Ticker or crypto symbol: BTC, ETH, NVDA, TSLA”windowstring“1h, 6h or 24h”
- hot_discussions
“Hot discussions merged from Hacker News, Lobsters and Lemmy: title, link, discussion URL, score, comments, heat.”
Publisher declares: read-only yes · open-world no
2 inputs
sourcestring“all, hn, lobsters or lemmy”limitinteger“Max discussions to return, default 30”
- trending_github_repos
“GitHub repositories gaining the most stars in the window, with language, topics and discussions linking them.”
Publisher declares: read-only yes · open-world no
3 inputs
windowstring“24h or 7d”languagestring or null“Primary language, e.g.”limitinteger“Max repos to return, default 25”
- social_network_stats
“Activity per network: Bluesky and Nostr posts per hour, fediverse size (FediDB), Hacker News items per hour.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
- social_history
“Stored hourly or daily history for a hashtag, a symbol (mentions and tone) or a GitHub repo (stars), newest first (Pro).”
Publisher declares: read-only yes · open-world no
4 inputs, 2 required
kindstringrequired“tag, symbol or repo”keystringrequired“The tag, the symbol (BTC) or the repo (owner/name)”resolutionstring“hour or day”limitinteger“Max points to return, default 60”
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
- 100% of 99
- Tools with a description
- 100% of 41
- Typical description length
- 106 characters
The tool set
Counted from the listing
- Tools
- 41
- Size of the list
- about 6,205 tokens for an agent to load (characters ÷ 4)
- Naming
- 41 of 41 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 41 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, comparing tools within groups of 40. 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://agentdataapi.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agentdata": {
"url": "https://agentdataapi.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"agentdata": {
"type": "http",
"url": "https://agentdataapi.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"agentdata","type":"http","url":"https://agentdataapi.com/mcp"}'Claude Code
claude mcp add --transport http agentdata https://agentdataapi.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"agentdata": {
"type": "streamableHttp",
"url": "https://agentdataapi.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"agentdata": {
"httpUrl": "https://agentdataapi.com/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.agentdata] url = "https://agentdataapi.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"agentdata": {
"url": "https://agentdataapi.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://agentdataapi.com/mcp --transport http
- Optional settings the entry also lists (left out above): X-API-Key.
- 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
- security.txt. No security.txt at https://agentdataapi.com/.well-known/ (HTTP 404, 2026-11-14). Source: agentdataapi.com/.well-known/security.txt · read 2026-11-14.
- A2A agent card. No A2A agent card at https://agentdataapi.com/.well-known/ (HTTP 404, 2026-11-14). Source: agentdataapi.com/.well-known/agent-card.json · read 2026-11-14.
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 #6The 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 says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint agentdataapi.com/mcp | Session opened | matches | our test · 2026-11-14 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-14 |
Tool list changes
Our reads compared · no tool calledHosted endpoint agentdataapi.com/mcp
1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-12 to 2026-11-14; versions 1.0.0 to 1.1.0).
Last change seen between our reads on 2026-11-12 (version 1.0.0) and 2026-11-14 (version 1.1.0).
Added (9):
hot_discussionssocial_historysocial_network_statssocial_symbol_mentionssocial_top_mentionssocial_topic_trendsocial_trending_linkssocial_trending_topicstrending_github_reposChanged (15):
list_capabilities: descriptionnews_sentiment_history: input schemanews_top_stories: input schemanews_trending: input schemanews_trending_people: input schemanews_trending_topics: input schemasensors_air_near: input schemasensors_quakes: input schemasensors_stations_near: input schemasensors_tide_predictions: input schemasensors_water_history: input schemaweather_alerts: input schemaweather_forecast: input schemaweather_forecast_daily: input schemaweather_stations_near: input schemaCompared 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 rating1 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.agentdataapi/agentdata
Answered from the data aboveWho publishes com.agentdataapi/agentdata?
The registry ties the namespace com.agentdataapi to the domain agentdataapi.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does com.agentdataapi/agentdata 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.agentdataapi/agentdata 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-inA 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.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- 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.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls 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-leakPlants 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
ssrfChecks 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-confirmationChecks 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-handlingSends 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
samplingChecks 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-dataChecks 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-boundaryChecks 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-channelChecks 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-hidingChecks 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-redirectChecks 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-deputyChecks 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
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks 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-validationChecks 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-schemeChecks 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.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,216 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 41 tools, 0 resources, 0 prompts.
- 4,478 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.
“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.agentdataapi/agentdata: MCP server record.” Data checked 2026-11-14. https://protocolprobe.com/mcp/servers/com.agentdataapi/agentdata
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
[](https://protocolprobe.com/mcp/servers/com.agentdataapi/agentdata)
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