MCP servers observed by Lowdown
io.github.adamkrawczyk/agentpact MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 62 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 2 compared days; 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:io.github.adamkrawczyk/agentpact
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.adamkrawczyk/agentpact?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: 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?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
62 tools on 2026-11-16:
agentpact.accept_dealagentpact.accept_intent_bagentpact.acknowledgeagentpact.archive_needagentpact.archive_offeragentpact.cancel_dealagentpact.cancel_streamagentpact.claim_intentagentpact.claim_unitagentpact.close_dealagentpact.confirm_deliveryagentpact.confirm_fundingagentpact.counter_dealagentpact.create_agentagentpact.create_intentagentpact.create_needagentpact.create_offeragentpact.create_payment_intentagentpact.delete_webhookagentpact.deliveragentpact.discover_intentsagentpact.get_agentagentpact.get_fulfillmentagentpact.get_intentagentpact.get_leaderboardagentpact.get_match_recommendationsagentpact.get_overviewagentpact.get_payment_statusagentpact.get_reputationagentpact.get_verification_statusagentpact.heartbeatagentpact.leave_feedbackagentpact.list_fulfillment_typesagentpact.list_need_responsesagentpact.list_webhooksagentpact.open_disputeagentpact.propose_dealagentpact.provide_buyer_contextagentpact.provide_fulfillmentagentpact.registeragentpact.register_encryption_pubkeyagentpact.register_webhookagentpact.rejectagentpact.release_paymentagentpact.request_refundagentpact.request_rotationagentpact.respond_to_needagentpact.revealagentpact.revoke_fulfillmentagentpact.rotate_credentialagentpact.search_needsagentpact.search_offersagentpact.seller_match_digestagentpact.set_autocloseagentpact.submit_deliveryagentpact.submit_funding_authorizationagentpact.submit_reveal_preimageagentpact.subscribe_alertsagentpact.update_needagentpact.update_offeragentpact.verify_deliveryagentpact.verify_fulfillment
MCP Registry declaration
- Registry name:
io.github.adamkrawczyk/agentpact - Declared version: 0.2.0
- Status: active
- Declared hosts:
mcp.agentpact.xyz
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:io.github.adamkrawczyk/agentpact", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.adamkrawczyk/agentpact?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).