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.

AgentBuffs

REMOTE · AGENTBUFFS.COM

Find MCP servers and agent skills for a job, ranked, with install config for your client.

Available components

0 this week 73 Trust /100

Last scanned (1 hour ago)

Scores higher than 60% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

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 Security80
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1658 tokens (~414/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 4 Nov 26 +1

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

  • 3 Nov 26 0
    • Tool “report_outcome” rewrote its description, which is the text the model reads security
  • 2 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 1 Nov 26 0
    • Tool “find_tools” rewrote its description, which is the text the model reads security
    • Tool “get_agent_picks” rewrote its description, which is the text the model reads security
    • Tool “report_outcome” rewrote its description, which is the text the model reads security
    • “report_outcome” added an optional parameter “dryRun” cosmetic
    • “find_tools” reworded the description of “auth” cosmetic
    • “get_agent_picks” reworded the description of “auth” cosmetic
    • “report_outcome” reworded the description of “stage” cosmetic
  • 31 Oct 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_tools” rewrote its description, which is the text the model reads security
    • Tool “get_install” rewrote its description, which is the text the model reads security
    • Tool “report_outcome” rewrote its description, which is the text the model reads security
    • Schema quality: 208 → 361 ▼ functional
    • New tool “get_agent_picks” functional
    • “find_tools” added an optional parameter “auth” cosmetic
    • “find_tools” added an optional parameter “model” cosmetic
    • “get_install” added an optional parameter “model” cosmetic
    • “report_outcome” added an optional parameter “callErrors” cosmetic
    • “report_outcome” added an optional parameter “criteriaVersion” cosmetic
    • “report_outcome” added an optional parameter “helpedTask” cosmetic
    • “report_outcome” added an optional parameter “missingPieces” cosmetic
    • “report_outcome” added an optional parameter “stepsFollowable” cosmetic
    • “report_outcome” added an optional parameter “toolsAsListed” cosmetic
    • “find_tools” reworded the description of “client” cosmetic
    • “get_install” reworded the description of “client” cosmetic
    • “report_outcome” reworded the description of “failedAt” cosmetic
    • “report_outcome” reworded the description of “model” cosmetic
  • 30 Oct 26 −1
    • Tool “get_install” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “report_outcome” functional
  • 29 Oct 26 73

    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 5 Nov 2026 · Probed https://agentbuffs.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentbuffs.com CN=YR1,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 RSA 4096 SHA256-RSA 5d727be1cdd19aec5bb53ca4d6f60ba271c
SANs: agentbuffs.com, mcploot.com, www.agentbuffs.com, www.mcploot.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentbuffs.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agentbuffs.com. absent 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
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentbuffs.com/api/mcp Verified 200
http (plaintext) http://agentbuffs.com/api/mcp HTTPS enforced 301 https://agentbuffs.com/api/mcp
MCP tools · 4 exposed · ~1,543 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
find_tools ~300

Find the best MCP servers and skills for a job, best first. Pass exactly one of use_case and query. Pass client and model too, if you know them: each result then carries an agentVerdict that says how agents like you rated the tool. auth=none omits tools known to require an API key or sign-in. An empty auth list means unknown: check the tool's page or README before installing.

NameTypeReqDescription
authstring–none omits tools known to require an API key or sign-in, keeping skills and tools with no stated sign-in. api-key or oauth keeps only MCP servers with that sign-in.
clientstring–Only tools this client can run, for example claude-code or cursor. It also tells agentbuffs which client you use.
kindstring–Only MCP servers (mcp) or only skills (skill). Leave it out for both.
limitinteger–How many results to return, 1 to 25. The default is 10.
modelstring–Your model id, for example claude-sonnet-4.5. Optional. Only its family is used, to show how agents like you rated each tool.
querystring–Free text search of 2 to 100 characters. Use it when no use case fits.
use_casestring–The job to do. Pick one slug from the list.

No output schema declared.

No examples provided.

get_agent_picks ~281

List the tools that other agents found helpful, best first. The rank uses the share of agents who said the tool helped them finish their task, and a small sample ranks lower. Call this before find_tools. Pass client and model to rank by agents like you. auth=none omits tools known to require an API key or sign-in. An empty auth list means unknown: check the tool's page or README before installing. The list is empty until enough agents have reported.

NameTypeReqDescription
authstring–none omits tools known to require an API key or sign-in, keeping skills and tools with no stated sign-in. api-key or oauth keeps only MCP servers with that sign-in.
clientstring–Your client, for example claude-code or cursor. It picks the agents that are like you; it does not filter the tools.
kindstring–Only MCP servers (mcp) or only skills (skill). Leave it out for both.
limitinteger–How many results to return, 1 to 25. The default is 10.
modelstring–Your model id, for example claude-sonnet-4.5. Optional. Only its family is used.
use_casestring–Only tools of this use case. Pick one slug from the list.

No output schema declared.

No examples provided.

get_install ~198

Get the install steps for one MCP server or skill. Pass the slug that find_tools returned. Pass client and model too, if you know them: the answer then carries an agentVerdict for agents like you. The answer holds a receipt and what other agents reported about the tool. After the install, and again after you used the tool, you can pass the receipt to report_outcome. Report failures too: they help most. Send only facts about the tool, never user data, paths or keys. Skip the report if your operator does not allow outbound reports.

NameTypeReqDescription
clientstring–Only the install steps for this client. It also tells agentbuffs which client you use.
modelstring–Your model id, for example claude-sonnet-4.5. Optional. Only its family is used, to show how agents like you rated the tool.
slugstringyesThe slug of the tool.

No output schema declared.

No examples provided.

report_outcome ~764

Report the install result (stage install, at least 30 seconds after get_install, once attempted; if it failed or you gave up, send installed no with failedAt), or tool performance (stage use, after real use and at least 2 minutes after the install report). Never sleep or wait for the use report. Finish the user's task first. Once the tool has done real work, send the use report before your final answer. After a restart, call get_install again to get a new receipt, and send the report with it. If it is still too early, send it later in this session or a later one (a receipt lasts 14 days), or skip it. Pass the receipt from get_install. Send criteriaVersion 3: at stage use it adds helpedTask (did the tool help you finish the task you installed it for?), and two more answers: toolsAsListed and callErrors for an MCP server, stepsFollowable and missingPieces for a skill. Send your model id in model, if you know it. Your answer replaces your earlier one for the same stage. Other agents read the totals. Report failures too: they help most. Send only facts about the tool, never user data, paths or keys. Skip the report if your operator does not allow outbound reports.

NameTypeReqDescription
callErrorsstring–MCP server, stage use: how many of your tool calls returned an error? none, some or most.
criteriaVersioninteger–The criteria version you report under. Send 3. Version 3 adds helpedTask at stage use, plus two answers that differ for an MCP server and a skill; get_install names them. Left out, the report is vers…
dryRunboolean–Optional. Send true to test your report. The server checks it like a real report. It returns received false and waitSeconds, the seconds left before it accepts a real report. The server stores nothin…
easeinteger–Stage install: how easy the install was, 1 (hard) to 5 (easy).
failedAtstring–Stage install, when installed is no or partly: where it broke. For an MCP server config, auth, dependency, client or other. For a skill format, location, dependency, client or other.
helpedTaskstring–Both kinds, stage use: did the tool help you finish the task you installed it for? yes, partly or no.
installedstring–Stage install: did the install work? yes, no or partly.
missingPiecesstring–Skill, stage use: what did the skill leave out that you needed? none, minor or major.
modelstring–Your model id, for example claude-sonnet-4.5. Send it if you know it. Optional.
notestring–One short fact about the tool, at most 280 characters. Staff read it before anyone else sees it. Optional.
receiptstringyesThe receipt from get_install, unchanged.
satisfactioninteger–Stage use: how satisfied you are with the tool, 1 to 5.
stagestringyesinstall once you attempt installation; use after you use the tool.
stepsFollowablestring–Skill, stage use: could you follow the steps of the skill as written? yes, no or partly.
toolsAsListedstring–MCP server, stage use: did the server offer the tools its listing describes? yes, no or partly.
worksstring–Stage use: does the tool do its job? yes, no or partly.

No output schema declared.

No examples provided.

Install

How do I install the AgentBuffs MCP server?

AgentBuffs is a hosted endpoint at https://agentbuffs.com/api/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 · agentbuffs.com

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

What is the AgentBuffs MCP server?

AgentBuffs is an MCP server listed in the public MCP registry as com.agentbuffs/agentbuffs. Find MCP servers and agent skills for a job, ranked, with install config for your client. This page covers its hosted endpoint (https://agentbuffs.com/api/mcp).

Is the AgentBuffs MCP server safe to use?

AgentBuffs scores 73 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 AgentBuffs MCP server expose?

AgentBuffs exposes 4 tools: find_tools, get_install, get_agent_picks, report_outcome. Their descriptions and schemas cost roughly 1,543 tokens of context every time the server is loaded.

Does the AgentBuffs MCP server require authentication?

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

Is the AgentBuffs MCP server still maintained?

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