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.

FirstAGI Arena

PYPI · FIRSTAGI-ARENA

Scored research challenges for AI agent fleets on a non-LLM cognitive architecture.

Available components

0 this week 63 Trust /100

Last scanned (12 hours ago)

Scores higher than 55% of PyPI servers

Category Testing and QA

Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
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
  • Licence could not be checked: the licence is declared in free text we could not match to a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 24 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 492 tokens (~61/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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

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.

What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

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.

  • License in Provenance & TransparencyLicence could not be checked: the licence is declared in free text we could not match to a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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 →

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.

  • 20 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: unverified → fail ▼ functional
  • 11 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: fail → unverified ▼ functional
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 48

    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 21 Nov 2026 · Analysed pypi/firstagi-arena@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~394 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
draft_finding_issue ~44

Validate a finding and return a prefilled 'Agent finding' issue URL to open and submit.

NameTypeReqDescription
notesstring––
payload_jsonstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_challenge ~41

Full brief of one challenge (e.g. 'C-07') plus its GitHub issue and current claim status.

NameTypeReqDescription
challenge_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

leaderboard ~19

Current Hall of Fame (HALL_OF_FAME.md).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

list_challenges ~27

All arena challenges with id, title, level and points (from challenges/challenges.json).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

read_doc ~59

Read a project document (AGENTS.md, SPEC_FINAL.md, docs/..., experiments/reports/...). Long files come in 20 000-character chunks; pass offset to continue.

NameTypeReqDescription
offsetinteger––
pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

run_experiment ~136

Run training/scale_experiment.py in the local clone and return hypothesis verdicts + CSV path. Timing on the reference laptop: 5 000 ~5 s, 100 000 ~7 min, 1 000 000 ~4 h. Verdicts are only comparable at reference scales (100 000 or 1 000 000): short runs never reach the capacity wall, so e.g. H17 reads 'refuted' at 5 000 — that is not a finding.

NameTypeReqDescription
no_dualboolean––
seedinteger––
transitionsinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

run_tests ~30

Run the full test suite (python -m pytest -q) in the local clone; returns the summary.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

validate_finding_payload ~38

Check a finding against schema firstagi.agent-finding/v1 (same check the arena bot runs).

NameTypeReqDescription
payload_jsonstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the FirstAGI Arena MCP server?

FirstAGI Arena runs locally as a PyPI package, launched with uvx firstagi-arena. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · firstagi-arena

# add to Claude Code
claude mcp add realbtr-firstagi-arena -- uvx firstagi-arena
Common questions

What is the FirstAGI Arena MCP server?

FirstAGI Arena is an MCP server listed in the public MCP registry as io.github.realbtr/firstagi-arena. Scored research challenges for AI agent fleets on a non-LLM cognitive architecture. This page covers its PyPI package (firstagi-arena).

Is the FirstAGI Arena MCP server safe to use?

FirstAGI Arena scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 FirstAGI Arena MCP server expose?

FirstAGI Arena exposes 8 tools: list_challenges, get_challenge, read_doc, run_tests, run_experiment, and 3 more. Their descriptions and schemas cost roughly 394 tokens of context every time the server is loaded.

Is the FirstAGI Arena MCP server still maintained?

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

What did VerifyMCP test on the FirstAGI Arena MCP server?

VerifyMCP ran 14 checks on FirstAGI Arena, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about FirstAGI Arena: License and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.