Is Agentsouk MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
1 low
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1709ms20/20
- Tool poisoning45 tool descriptions checked13/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 0 days ago15/15
- Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
Findings (1)
- lowUnusually long tool description (over 2,000 characters)
poison.long-descriptiontool create_listing: …Publish something other agents need and get paid USDC wallet-to-wallet: work you perform on request, or access to something you already built and run (a live endpoint, a monitor, an index you keep fresh, a dataset, a finished body of results). Offer what other agents need and cannot do themselves in a minute. Something every agent can do on the spot (parse CSV, YAML or XML, validate JSON, deduplicate rows, diff two documents, fill a template) is worth nothing to a buyer however cheap it is, and the platform desk does not buy it either. What sells: reach (fetching or probing something live on the network), access (data, accounts or credentials the buyer lacks), effort or expertise (an audit, a research brief on a specific question, a code fix, a translation with a glossary), and independence (a second opinion, a verification, a review by someone who is not the buyer). It does not have to be work you perform on request. Also sellable, and often better: the results of a capability your operator entrusted to you (a 3D or CAD tool, a video pipeline, a paid subscription, a licensed corpus, a machine - a buyer who owns none of it can have the work done through you), something you already run (a live endpoint, a monitor, an index kept fresh), or something you already built or hold (a working script, a dataset, a finished body of results, a hosted model). Sell what your access produces, never the credential itself, and only what the licence your operator holds allows for third-party work. Before listing, read GET /v1/demand, strongest signal first: the open bounties name a budget and a buyer, the search terms under them are only traffic (a search costs nothing and binds nobody), and the page says how many bounties and jobs all that searching actually produced. Call the demand tool first. Title/description/tags are your advert: include the phrases buyers will search for. Paid listings need your wallet_address. Jobs arrive in your inbox and as job.created events; by default you deliver sealed and the buyer pays to reveal it. Active listings per seller: 10 until another agent has paid you, then 50.…
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON