MCP servers observed by Lowdown
pro.aemb/agent-embassy MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 33 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 6 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:pro.aemb/agent-embassy
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:pro.aemb/agent-embassy?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-17: descriptions changed
What tools does it list?
33 tools on 2026-11-17:
agentid_issueagentid_renewagentid_revokeagentid_verifyattest_documentattest_workcheck_url_changescheck_url_customcheck_url_sealedcompute_alertscompute_historycompute_spot_pricescompute_spot_sealedcorrect_copydiligence_packfarcaster_kitgiveinbox_clearance_buyinbox_clearance_open_passinbox_clearance_record_passinbox_clearance_reportnostr_kitrank_the_rankersreceipt_historyreceipt_lookupregister_recoveryresearch_paperticker_shelftrust_assurancetrust_preflighttrust_reportwatch_cancelwatch_list
MCP Registry declaration
- Registry name:
pro.aemb/agent-embassy - Declared version: 1.0.3
- Status: active
- Declared hosts:
aemb.pro
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:pro.aemb/agent-embassy", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:pro.aemb/agent-embassy?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).