Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentDataAPI

REMOTE · AGENTDATAAPI.COM

Grid power prices and carbon, open sensors, weather alerts and forecasts, news and social signals.

Available components

+3 this week 75 Trust /100

Last scanned (15 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3508 tokens (~85/item across 41 items; 41 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 41 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 42 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +2
    • Tool “list_capabilities” rewrote its description, which is the text the model reads security
    • Schema quality: 75 → 85 ▼ functional
    • Tool coverage: 63% → 100% ▲ functional
    • “hot_discussions” reworded the description of “limit” cosmetic
    • “news_sentiment_history” reworded the description of “entity” cosmetic
    • “news_sentiment_history” reworded the description of “limit” cosmetic
    • “news_top_stories” reworded the description of “limit” cosmetic
    • “news_trending” reworded the description of “limit” cosmetic
    • “news_trending” reworded the description of “window” cosmetic
    • “news_trending_people” reworded the description of “limit” cosmetic
    • “news_trending_topics” reworded the description of “limit” cosmetic
    • “sensors_air_near” reworded the description of “lat” cosmetic
    • “sensors_air_near” reworded the description of “lon” cosmetic
    • “sensors_air_near” reworded the description of “radius_km” cosmetic
    • “sensors_quakes” reworded the description of “hours” cosmetic
    • “sensors_quakes” reworded the description of “lat” cosmetic
    • “sensors_quakes” reworded the description of “lon” cosmetic
    • “sensors_quakes” reworded the description of “min_mag” cosmetic
    • “sensors_quakes” reworded the description of “radius_km” cosmetic
    • “sensors_stations_near” reworded the description of “lat” cosmetic
    • “sensors_stations_near” reworded the description of “lon” cosmetic
    • “sensors_stations_near” reworded the description of “radius_km” cosmetic
    • “sensors_tide_predictions” reworded the description of “station” cosmetic
    • “sensors_water_history” reworded the description of “limit” cosmetic
    • “sensors_water_history” reworded the description of “site” cosmetic
    • “social_history” reworded the description of “limit” cosmetic
    • “social_top_mentions” reworded the description of “limit” cosmetic
    • “social_trending_links” reworded the description of “limit” cosmetic
    • “social_trending_topics” reworded the description of “limit” cosmetic
    • “trending_github_repos” reworded the description of “limit” cosmetic
    • “weather_alerts” reworded the description of “limit” cosmetic
    • “weather_forecast” reworded the description of “hours” cosmetic
    • “weather_forecast” reworded the description of “lat” cosmetic
    • “weather_forecast” reworded the description of “lon” cosmetic
    • “weather_forecast_daily” reworded the description of “days” cosmetic
    • “weather_forecast_daily” reworded the description of “lat” cosmetic
    • “weather_forecast_daily” reworded the description of “lon” cosmetic
    • “weather_stations_near” reworded the description of “lat” cosmetic
    • “weather_stations_near” reworded the description of “lon” cosmetic
    • “weather_stations_near” reworded the description of “radius_km” cosmetic
  • 13 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 2422 → 3097 ▼ functional
    • New tool “hot_discussions” functional
    • New tool “social_history” functional
    • New tool “social_network_stats” functional
    • New tool “social_symbol_mentions” functional
    • New tool “social_top_mentions” functional
    • New tool “social_topic_trend” functional
    • New tool “social_trending_links” functional
    • New tool “social_trending_topics” functional
    • New tool “trending_github_repos” functional
  • 12 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://agentdataapi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentdataapi.com CN=YE1,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA384 64012c35ab960ea1c60556aa34923a523c9
SANs: *.agentdataapi.com, agentdataapi.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentdataapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
agentdataapi.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentdataapi.com/mcp Verified 200
http (plaintext) http://agentdataapi.com/mcp HTTPS enforced 301 https://agentdataapi.com/mcp
MCP tools · 41 exposed · ~3,135 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_free_api_key ~59

Create a FREE AgentDataAPI key (no signup) valid for every slice. Returned once; add it to the server's X-API-Key header.

NameTypeReqDescription
emailstringyesYour human's real email, else your own agent mailbox.

No output schema declared.

No examples provided.

grid_carbon ~63

GB grid carbon intensity in gCO2/kWh: actual and forecast now, the next 6 hours, and the regional generation mix.

NameTypeReqDescription
regionstring–GB for national, or a NESO region id 1 to 17 (13 = London)

No output schema declared.

No examples provided.

grid_cheapest_window ~109

Cheapest contiguous window of N hours in the next horizon from day-ahead or pre-dispatch prices (GB: greenest window from the carbon forecast).

NameTypeReqDescription
horizoninteger–Look-ahead in hours
hoursinteger–Window length in hours
marketstringyesnem (Australia), gb, eu or us
regionstringyesRegion code, e.g. NSW1, GB, DE_LU, CAISO. List them with grid_regions.

No output schema declared.

No examples provided.

grid_day_ahead ~102

Day-ahead (EU) or pre-dispatch (NEM) prices per interval for a local day, with min, max, average and negative intervals.

NameTypeReqDescription
date––Local calendar day YYYY-MM-DD, default tomorrow
marketstringyesnem (Australia), gb, eu or us
regionstringyesRegion code, e.g. NSW1, GB, DE_LU, CAISO. List them with grid_regions.

No output schema declared.

No examples provided.

grid_generation ~74

Latest generation mix for a region: MW per fuel, total and renewables share (basis points).

NameTypeReqDescription
marketstringyesnem (Australia), gb, eu or us
regionstringyesRegion code, e.g. NSW1, GB, DE_LU, CAISO. List them with grid_regions.

No output schema declared.

No examples provided.

grid_load ~63

Latest grid demand for a region in MW.

NameTypeReqDescription
marketstringyesnem (Australia), gb, eu or us
regionstringyesRegion code, e.g. NSW1, GB, DE_LU, CAISO. List them with grid_regions.

No output schema declared.

No examples provided.

grid_price ~78

Latest settled wholesale electricity price for a region (micro units of local currency, USD conversion, demand, negative-price flag).

NameTypeReqDescription
marketstringyesnem (Australia), gb, eu or us
regionstringyesRegion code, e.g. NSW1, GB, DE_LU, CAISO. List them with grid_regions.

No output schema declared.

No examples provided.

grid_price_history ~118

Settled prices for the last 7 days (Pro), optionally averaged per 30 or 60 minutes.

NameTypeReqDescription
from––ISO UTC start, default 7 days ago
intervalstring–native, 30m or 60m
marketstringyesnem (Australia), gb, eu or us
regionstringyesRegion code, e.g. NSW1, GB, DE_LU, CAISO. List them with grid_regions.
to––ISO UTC end, default now

No output schema declared.

No examples provided.

grid_regions ~44

Every power market region we serve: code, market, timezone, currency, source and price cadence.

NameTypeReqDescription
market––nem, gb, eu or us; omit for all

No output schema declared.

No examples provided.

hot_discussions ~66

Hot discussions merged from Hacker News, Lobsters and Lemmy: title, link, discussion URL, score, comments, heat.

NameTypeReqDescription
limitinteger–Max discussions to return, default 30
sourcestring–all, hn, lobsters or lemmy

No output schema declared.

No examples provided.

list_capabilities ~38

What this server offers across energy, sensors, weather, news and social: endpoints, prices and the first calls to make. No key needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

news_search_entities ~69

Search the tracked entities (organisations, tickers, crypto assets, central banks, governments, topics) and get their ids.

NameTypeReqDescription
kind––org, ticker, crypto, central_bank, government, topic
query––Free text: 'nvidia', 'fed', 'bitcoin'

No output schema declared.

No examples provided.

news_sentiment ~75

News tone (bps), mentions against the 30-day baseline, volume ratio, novelty and top themes for one entity.

NameTypeReqDescription
entitystringyesEntity id such as org_nvidia, cb_federal_reserve, asset_bitcoin
windowstring–1h, 24h or 7d

No output schema declared.

No examples provided.

news_sentiment_history ~81

Mentions and tone per window or per day for an entity (Pro), newest first.

NameTypeReqDescription
entitystringyesEntity id such as org_nvidia, cb_federal_reserve, asset_bitcoin
intervalstring–15m or 1d
limitinteger–Max points to return, default 60

No output schema declared.

No examples provided.

news_ticker_score ~67

News score for a ticker: how unusual the coverage volume is and how its tone compares with normal.

NameTypeReqDescription
symbolstringyesTicker or crypto symbol: NVDA, JPM, BTC
windowstring–1h, 24h or 7d

No output schema declared.

No examples provided.

news_top_stories ~74

The most-covered stories in the window (title, link, publisher, tone), never article text.

NameTypeReqDescription
entity––Only stories naming this entity id
limitinteger–Max stories to return, default 20
windowstring–1h, 6h or 24h

No output schema declared.

No examples provided.

news_trending ~77

Entities with the most unusual news volume in the window, ranked by novelty against their baseline.

NameTypeReqDescription
kind––ticker, crypto, org, central_bank, government, topic
limitinteger–Max entities to return, default 20
windowstring–1h, 24h or 7d

No output schema declared.

No examples provided.

news_trending_people ~63

Public figures with the biggest attention spike (Wikipedia pageviews and news coverage over their 30-day baseline), by category.

NameTypeReqDescription
category––celebrity, politics, sport, business, other
limitinteger–Max people to return, default 20

No output schema declared.

No examples provided.

news_trending_topics ~57

Trending topics for a region: top daily searches with headlines, trending Mastodon tags and shared links.

NameTypeReqDescription
limitinteger–Max topics to return, default 20
regionstring–US, AU or GB

No output schema declared.

No examples provided.

petroleum_weekly ~52

Latest EIA weekly US petroleum inventory figure with the previous week and the change.

NameTypeReqDescription
seriesstring–crude_stocks, gasoline_stocks, distillate_stocks, refinery_inputs or crude_imports

No output schema declared.

No examples provided.

sensors_air ~43

Latest air quality readings and US EPA AQI at one monitor.

NameTypeReqDescription
station_idstringyesopenaq_{location_id}, e.g. openaq_2178

No output schema declared.

No examples provided.

sensors_air_near ~105

Air quality monitors near a point with latest readings (PM2.5, PM10, O3, NO2, SO2, CO) and AQI, nearest first.

NameTypeReqDescription
latnumberyesLatitude in decimal degrees, e.g. -33.87
lonnumberyesLongitude in decimal degrees, e.g. 151.21
radius_kmnumber–Search radius in km, default 25, max 500

No output schema declared.

No examples provided.

sensors_quakes ~124

Earthquakes in the last N hours from USGS, optionally above a magnitude and within a radius of a point.

NameTypeReqDescription
hoursinteger–Look-back window in hours, default 24, max 720
lat––Centre latitude in decimal degrees; with lon and radius_km limits results to a circle
lon––Centre longitude in decimal degrees
min_mag––Minimum magnitude, e.g. 4.5; omit for all
radius_km––Radius in km around lat/lon, max 20000

No output schema declared.

No examples provided.

sensors_stations_near ~134

Stations of every open sensor network near a point, nearest first, with distance and parameters.

NameTypeReqDescription
latnumberyesLatitude in decimal degrees, e.g. -33.87
lonnumberyesLongitude in decimal degrees, e.g. 151.21
network––usgs, coops or openaq
parameter––pm25, pm10, o3, no2, so2, co, gage_height, discharge, water_temp, water_level
radius_kmnumber–Search radius in km, default 25, max 500

No output schema declared.

No examples provided.

sensors_tide_predictions ~64

Predicted high and low tides for a day at a NOAA tide station.

NameTypeReqDescription
date––YYYY-MM-DD (UTC), default today
stationstringyesNOAA CO-OPS station id, e.g. 8518750 (The Battery, NY)

No output schema declared.

No examples provided.

sensors_tides ~58

Latest observed water level (metres MLLW) at a NOAA tide station with the next high and low.

NameTypeReqDescription
stationstringyesNOAA CO-OPS station id, e.g. 8518750 (The Battery, NY)

No output schema declared.

No examples provided.

sensors_water_gauge ~57

Latest river gauge height, discharge and water temperature at a USGS site, with NWS flood stage status.

NameTypeReqDescription
sitestringyesUSGS site number, e.g. 01646500 (Potomac at Little Falls)

No output schema declared.

No examples provided.

sensors_water_history ~86

Gauge readings for the last 7 days at a USGS site, newest first (Pro).

NameTypeReqDescription
end––ISO time, latest
limitinteger–Max readings to return, default 500
sitestringyesUSGS site number, e.g. 01646500 (Potomac at Little Falls)
start––ISO time, earliest

No output schema declared.

No examples provided.

social_history ~95

Stored hourly or daily history for a hashtag, a symbol (mentions and tone) or a GitHub repo (stars), newest first (Pro).

NameTypeReqDescription
keystringyesThe tag, the symbol (BTC) or the repo (owner/name)
kindstringyestag, symbol or repo
limitinteger–Max points to return, default 60
resolutionstring–hour or day

No output schema declared.

No examples provided.

social_network_stats ~36

Activity per network: Bluesky and Nostr posts per hour, fediverse size (FediDB), Hacker News items per hour.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

social_symbol_mentions ~74

Social volume and tone for one ticker or coin: mentions per network against its baseline, spike, trend and discussions naming it.

NameTypeReqDescription
symbolstringyesTicker or crypto symbol: BTC, ETH, NVDA, TSLA
windowstring–1h, 6h or 24h

No output schema declared.

No examples provided.

social_top_mentions ~79

Stocks and crypto assets ranked by social attention: mentions against a 30-day baseline, spike, lexicon tone, discussions.

NameTypeReqDescription
limitinteger–Max symbols to return, default 20
typestring–all, crypto or stock
windowstring–1h, 6h or 24h

No output schema declared.

No examples provided.

social_topic_trend ~75

One hashtag across networks: mentions per network, expected count, spike, trend, first seen and the last 24 hours by hour.

NameTypeReqDescription
tagstringyesA hashtag without #: 'bitcoin', 'ai', 'f1'
windowstring–1h, 6h or 24h

No output schema declared.

No examples provided.

social_trending_links ~84

The most-shared URLs across networks with titles, shares per network and the Hacker News, Lobsters or Lemmy discussions about them.

NameTypeReqDescription
domain––Only this domain, e.g. github.com
limitinteger–Max links to return, default 25
windowstring–1h, 6h or 24h

No output schema declared.

No examples provided.

social_trending_topics ~89

Trending hashtags across Bluesky, Mastodon and Nostr (mentions x spike against each tag's baseline), plus Bluesky's own trends list.

NameTypeReqDescription
limitinteger–Max tags to return, default 25
networkstring–all, bluesky, mastodon or nostr
windowstring–1h, 6h or 24h

No output schema declared.

No examples provided.

trending_github_repos ~74

GitHub repositories gaining the most stars in the window, with language, topics and discussions linking them.

NameTypeReqDescription
language––Primary language, e.g. Rust, Python
limitinteger–Max repos to return, default 25
windowstring–24h or 7d

No output schema declared.

No examples provided.

weather_alerts ~98

Active weather alerts for a region, severity first. US from the National Weather Service; Australia from the Bureau of Meteorology where licensed.

NameTypeReqDescription
limitinteger–Max alerts to return, default 100
regionstringyesUS state (TX), NWS zone or county code (TXZ229), Australian state (NSW), or US / AU
severity––Extreme, Severe, Moderate, Minor or Unknown

No output schema declared.

No examples provided.

weather_current ~60

Current conditions at the nearest reporting station (within 150 km) in the United States or Australia.

NameTypeReqDescription
latnumberyesLatitude, e.g. -33.87
lonnumberyesLongitude, e.g. 151.21

No output schema declared.

No examples provided.

weather_forecast ~94

Hourly GFS forecast (temperature, humidity, wind, gust, precipitation, cloud) for a point in the contiguous US or Australia.

NameTypeReqDescription
hoursinteger–Forecast horizon in hours, default 48, max 120
latnumberyesLatitude in decimal degrees, e.g. -33.87
lonnumberyesLongitude in decimal degrees, e.g. 151.21

No output schema declared.

No examples provided.

weather_forecast_daily ~92

Daily forecast summary (min and max temperature, wind, gust, precipitation total) for a point in the contiguous US or Australia.

NameTypeReqDescription
daysinteger–Number of days, default 3, max 5
latnumberyesLatitude in decimal degrees, e.g. -33.87
lonnumberyesLongitude in decimal degrees, e.g. 151.21

No output schema declared.

No examples provided.

weather_stations_near ~85

Reporting stations near a point in the United States or Australia, nearest first.

NameTypeReqDescription
latnumberyesLatitude in decimal degrees, e.g. -33.87
lonnumberyesLongitude in decimal degrees, e.g. 151.21
radius_kmnumber–Search radius in km, default 50, max 500

No output schema declared.

No examples provided.

Install

How do I install the AgentDataAPI MCP server?

AgentDataAPI is a hosted endpoint at https://agentdataapi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agentdataapi.com

# add to Claude Code
claude mcp add --transport http com-agentdataapi-agentdata 'https://agentdataapi.com/mcp'
Common questions

What is the AgentDataAPI MCP server?

AgentDataAPI is an MCP server listed in the public MCP registry as com.agentdataapi/agentdata. Grid power prices and carbon, open sensors, weather alerts and forecasts, news and social signals. This page covers its hosted endpoint (https://agentdataapi.com/mcp).

Is the AgentDataAPI MCP server safe to use?

AgentDataAPI scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AgentDataAPI MCP server expose?

AgentDataAPI exposes 41 tools: list_capabilities, create_free_api_key, grid_regions, grid_price, grid_day_ahead, and 36 more. Their descriptions and schemas cost roughly 3,135 tokens of context every time the server is loaded.

Does the AgentDataAPI MCP server require authentication?

No. We connected to AgentDataAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentDataAPI MCP server still maintained?

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

What did VerifyMCP test on the AgentDataAPI MCP server?

VerifyMCP ran 13 checks on AgentDataAPI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.