agentprobe.org
031 ms1,000 ms2026-09-07T01:51:17+00:00 · auth-required · 79 ms2026-09-08T07:48:11+00:00 · connect-fail · 170 ms2026-09-09T08:04:07+00:00 · auth-required · 393 ms2026-09-10T08:04:27+00:00 · auth-required · 95 ms2026-09-11T09:05:05+00:00 · auth-required · 550 ms2026-09-12T10:03:25+00:00 · auth-required · 347 ms2026-09-07 01:512026-09-12 10:03031 ms1,000 ms2026-09-07T01:51:17+00:00 · auth-required · 79 ms2026-09-08T07:48:11+00:00 · connect-fail · 170 ms2026-09-09T08:04:07+00:00 · auth-required · 393 ms2026-09-10T08:04:27+00:00 · auth-required · 95 ms2026-09-11T09:05:05+00:00 · auth-required · 550 ms2026-09-12T10:03:25+00:00 · auth-required · 347 ms2026-09-07 01:512026-09-12 10:03
probe history, latency (log) over time, glyph = outcome
B grade
auth-required
30 score
347 ms
83.3% uptime over 6 measured probes
AS16509 AMAZON-02 - Amazon.com, Inc., US · US

https://api.scentrev.com/mcp/

mcp first seen 2026-09-07 · last seen 2026-09-12 · json

Listed in

sourcenamedescriptionexternal id
Agenstryscentrev mcpmcp:mcp.so:shashankkandimalla/api-89d352

Same host

agents-txt × 1 ard × 1 llms-txt × 1 robots × 1 sigdir × 1

Badge

agentprobe grade B

embed:

<a href="https://agentprobe.org/endpoint/146285"><img src="https://agentprobe.org/badge/146285.svg" alt="agentprobe"></a>

Probe history

probed (UTC)outcomescorestatushttpmsversioncapabilitieserror
2026-09-12 10:03auth-required30 401HTTP/1.1347
details

meta

{"final_url":"https://api.scentrev.com/mcp/","www_authenticate":"Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://api.scentrev.com/.well-known/oauth-protected-resource\"","oauth":{"prm_url":"https://api.scentrev.com/.well-known/oauth-protected-resource","resource":"https://api.scentrev.com/mcp","authorization_servers":["https://gipvypdyivrczfcwekkt.supabase.co/auth/v1"],"scopes_supported":["openid","email"]},"http_version":"HTTP/1.1","vantage":"us-east-1"}
HTTP 401
2026-09-11 09:05auth-required30 401HTTP/1.1550
details

meta

{"final_url":"https://api.scentrev.com/mcp/","www_authenticate":"Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://api.scentrev.com/.well-known/oauth-protected-resource\"","oauth":{"prm_url":"https://api.scentrev.com/.well-known/oauth-protected-resource","resource":"https://api.scentrev.com/mcp","authorization_servers":["https://gipvypdyivrczfcwekkt.supabase.co/auth/v1"],"scopes_supported":["openid","email"]},"http_version":"HTTP/1.1","vantage":"us-east-1"}
HTTP 401
2026-09-10 08:04auth-required30 401HTTP/1.195
details

meta

{"final_url":"https://api.scentrev.com/mcp/","www_authenticate":"Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://api.scentrev.com/.well-known/oauth-protected-resource\"","oauth":{"prm_url":"https://api.scentrev.com/.well-known/oauth-protected-resource","resource":"https://api.scentrev.com/mcp","authorization_servers":["https://gipvypdyivrczfcwekkt.supabase.co/auth/v1"],"scopes_supported":["openid","email"]},"http_version":"HTTP/1.1","vantage":"us-east-1"}
HTTP 401
2026-09-09 08:04auth-required30 401393
details

meta

{"final_url":"https://api.scentrev.com/mcp/","www_authenticate":"Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://api.scentrev.com/.well-known/oauth-protected-resource\"","oauth":{"prm_url":"https://api.scentrev.com/.well-known/oauth-protected-resource","resource":"https://api.scentrev.com/mcp","authorization_servers":["https://gipvypdyivrczfcwekkt.supabase.co/auth/v1"],"scopes_supported":["openid","email"]},"vantage":"us-east-1"}
HTTP 401
2026-09-08 07:48connect-fail 170
details

meta

{"vantage":"us-east-1"}
WriteError:
2026-09-07 01:51auth-required30 40179
details

meta

{"final_url":"https://api.scentrev.com/mcp/","www_authenticate":"Bearer error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://api.scentrev.com/.well-known/oauth-protected-resource\"","oauth":{"prm_url":"https://api.scentrev.com/.well-known/oauth-protected-resource","resource":"https://api.scentrev.com/mcp","authorization_servers":["https://gipvypdyivrczfcwekkt.supabase.co/auth/v1"],"scopes_supported":["openid","email"]}}