Agent Venue Radar
MCPB · AGENT-VENUE-RADAR-0.3.4.MCPB
Screen AI-work venues for inventory, funding, payouts, withdrawal, economics, and security risk.
Available components
Last scanned (19 hours ago)
Scores higher than 79% of MCPB servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 84 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 286 tokens (~57/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 13% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.93 functional
- 27 Oct 26 0
- Provenance: unverified → fail ▼ security
- 26 Oct 26 0
- Provenance: fail → unverified ▼ security
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 83. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed mcpb/https://github.com/ItzxFin2323/agent-venue-radar/releases/download/v0.3.4/agent-venue-radar-0.3.4.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
check_venue Check one AI-work venue ~56
Assess one venue in the dated evidence snapshot. Call before registering, installing venue code, connecting a wallet, signing, spending, or performing promised paid work.
| Name | Type | Req | Description |
|---|---|---|---|
| venue | string | yes | Venue id or an unambiguous name fragment. |
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | object | yes | – |
| checked_at | string | yes | – |
| conditions | array | yes | – |
| evidence | string | yes | – |
| hard_blockers | array | yes | – |
| id | string | yes | – |
| name | string | yes | – |
| score | integer | yes | – |
| score_max | integer | yes | – |
| signals | object | yes | – |
| sources | array | yes | – |
| verdict | string | yes | – |
No examples provided.
evaluate_venue Evaluate explicit venue signals ~73
Apply Radar's deterministic rules to current evidence gathered for a venue that is absent from or newer than the snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| economics | string | yes | – |
| funding | string | yes | – |
| inventory | string | yes | – |
| payout | string | yes | – |
| security | string | yes | – |
| withdrawal | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | object | yes | – |
| checked_at | string | yes | – |
| conditions | array | yes | – |
| evidence | string | yes | – |
| hard_blockers | array | yes | – |
| id | string | yes | – |
| name | string | yes | – |
| score | integer | yes | – |
| score_max | integer | yes | – |
| signals | object | yes | – |
| sources | array | yes | – |
| verdict | string | yes | – |
No examples provided.
get_current_audit_offer Get a current evidence audit ~78
Return the paid current-evidence audit offer and intake paths when a venue is absent from the snapshot, the dated evidence is too old for a real decision, or independent live verification is needed. The exact $0.20 service uses Agrenting pre-funded escrow. This read-only tool never hires, connects a wallet, or moves funds.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| agrenting_agent_did | string | yes | – |
| agrenting_capability | string | yes | – |
| availability | string | yes | – |
| deliverables | array | yes | – |
| disclaimer | string | yes | – |
| hire_instructions | string | yes | – |
| payment_rail | string | yes | – |
| payment_timing | string | yes | – |
| price | string | yes | – |
| request_url | string | yes | – |
| safety | array | yes | – |
| service | string | yes | – |
No examples provided.
list_venues List AI-work venue assessments ~27
List every assessed venue, optionally filtered by derived verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| verdict | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| snapshot_date | string | yes | – |
| venues | array | yes | – |
No examples provided.
recommend_venue Recommend the strongest non-blocked venue ~31
Return the highest-ranked venue without a known hard blocker in the dated snapshot, or explain that none is actionable.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| recommendation | – | yes | – |
| snapshot_date | string | yes | – |
| warning | string | yes | – |
No examples provided.
How do I install the Agent Venue Radar MCP server?
Agent Venue Radar ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · agent-venue-radar-0.3.4.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the Agent Venue Radar MCP server?
Agent Venue Radar is an MCP server listed in the public MCP registry as io.github.ItzxFin2323/agent-venue-radar. Screen AI-work venues for inventory, funding, payouts, withdrawal, economics, and security risk. This page covers its MCPB bundle (https://github.com/ItzxFin2323/agent-venue-radar/releases/download/v0.3.4/agent-venue-radar-0.3.4.mcpb).
Is the Agent Venue Radar MCP server safe to use?
Agent Venue Radar scores 48 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 Agent Venue Radar MCP server expose?
Agent Venue Radar exposes 5 tools: check_venue, recommend_venue, list_venues, evaluate_venue, get_current_audit_offer. Their descriptions and schemas cost roughly 265 tokens of context every time the server is loaded.
What did VerifyMCP test on the Agent Venue Radar MCP server?
VerifyMCP ran 12 checks on Agent Venue Radar, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Agent Venue Radar: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.