Feagi MCP Server

feagi-mcp PyPI v0.0.6

Published by neuraville — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (setup.py)MTC-SRC-002

In the server's implementation (`setup.py:56`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: nvironment...") subprocess.run([sys.executable, "-m", "venv", "venv"], check=True) print("✓ Virtual envi

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server setup.py

low Dynamic module load from a non-literal in packaging/dev tooling (scripts/verify_install.py)MTC-SRC-005

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/verify_install.py:25`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ed.""" try: __import__(module) print(f"✓ {description}") return True except ImportError

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/verify_install.py

Tools 98

Each tool and what it can reach — statically extracted from the published source.

  • composer_download_simulator_pack_bundleingests untrusted input
  • composer_get_simulator_pack_resolvedingests untrusted input
  • download_genomeingests untrusted input
  • download_region_genomeingests untrusted input
  • auto_polarity_probeno sensitive capability
  • brain_visualizer_apino sensitive capability
  • build_reflex_mappingno sensitive capability
  • clone_cortical_areano sensitive capability
  • composer_get_simulator_pack_versionsno sensitive capability
  • composer_list_simulator_packsno sensitive capability
Show 88 more tools ↓
  • compute_io_cortical_idno sensitive capability
  • confirm_amalgamation_destinationno sensitive capability
  • control_burst_engineno sensitive capability
  • create_brain_regionno sensitive capability
  • create_cortical_areano sensitive capability
  • create_io_area_for_unitno sensitive capability
  • create_morphologyno sensitive capability
  • delete_cortical_areano sensitive capability
  • delete_cortical_mappingno sensitive capability
  • delete_genome_snapshotno sensitive capability
  • embodiment_discover_introspection_endpointno sensitive capability
  • embodiment_get_physics_stateno sensitive capability
  • embodiment_reset_simulation_time_statsno sensitive capability
  • embodiment_set_joint_stateno sensitive capability
  • get_agent_connection_endpointsno sensitive capability
  • get_agent_device_registrationsno sensitive capability
  • get_agent_joint_mapno sensitive capability
  • get_agent_propertiesno sensitive capability
  • get_area_parametersno sensitive capability
  • get_area_semantic_infono sensitive capability
  • get_brain_regionsno sensitive capability
  • get_burst_counterno sensitive capability
  • get_burst_engine_configno sensitive capability
  • get_burst_engine_statusno sensitive capability
  • get_connectivityno sensitive capability
  • get_connectivity_summaryno sensitive capability
  • get_controller_lifecycle_eventsno sensitive capability
  • get_cortical_area_geometryno sensitive capability
  • get_cortical_id_name_mappingno sensitive capability
  • get_cortical_map_detailedno sensitive capability
  • get_cortical_mappingno sensitive capability
  • get_cortical_synapse_countsno sensitive capability
  • get_cortical_templateno sensitive capability
  • get_embodiment_statusno sensitive capability
  • get_experiment_stop_causeno sensitive capability
  • get_feagi_link_healthno sensitive capability
  • get_genome_file_nameno sensitive capability
  • get_genome_infono sensitive capability
  • get_log_tailno sensitive capability
  • get_motor_snapshot_lastno sensitive capability
  • get_neuron_state_by_idno sensitive capability
  • get_registered_agentsno sensitive capability
  • get_runtime_metricsno sensitive capability
  • get_sensor_snapshot_lastno sensitive capability
  • get_voxel_neuronsno sensitive capability
  • health_checkno sensitive capability
  • inspect_cortical_areano sensitive capability
  • inspect_cortical_areas_batchno sensitive capability
  • inspect_cortical_areas_minimalno sensitive capability
  • inspect_neuron_state_atno sensitive capability
  • interpret_cortical_idno sensitive capability
  • list_agent_capabilities_allno sensitive capability
  • list_area_synapsesno sensitive capability
  • list_brain_visualizer_operationsno sensitive capability
  • list_controller_bridgesno sensitive capability
  • list_cortical_area_namesno sensitive capability
  • list_cortical_areasno sensitive capability
  • list_genome_snapshotsno sensitive capability
  • list_ipu_areasno sensitive capability
  • list_ipu_areas_with_metadatano sensitive capability
  • list_morphologiesno sensitive capability
  • list_morphologies_summaryno sensitive capability
  • list_opu_areasno sensitive capability
  • list_opu_areas_with_metadatano sensitive capability
  • load_barebones_genomeno sensitive capability
  • load_genome_from_fileno sensitive capability
  • monitor_activityno sensitive capability
  • monitor_activity_batchno sensitive capability
  • pause_burst_engineno sensitive capability
  • probe_area_responseno sensitive capability
  • queue_amalgamation_by_payloadno sensitive capability
  • reset_cortical_neural_stateno sensitive capability
  • resolve_cortical_area_by_nameno sensitive capability
  • restore_genome_snapshotno sensitive capability
  • resume_burst_engineno sensitive capability
  • save_genome_to_filesystemno sensitive capability
  • send_motor_commandno sensitive capability
  • set_burst_engine_frequencyno sensitive capability
  • snapshot_genomeno sensitive capability
  • stimulate_areano sensitive capability
  • stimulate_area_batchno sensitive capability
  • suggest_cortical_anchor_positionsno sensitive capability
  • trace_signal_pathno sensitive capability
  • update_cortical_areano sensitive capability
  • update_cortical_mappingno sensitive capability
  • upload_genomeno sensitive capability
  • validate_brain_region_hierarchyno sensitive capability
  • validate_genomeno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.0.6 latest A 93/100 2 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/feagi-mcp/badge.svg)](https://mcptrustchecker.com/registry/feagi-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/feagi-mcp"><img src="https://mcptrustchecker.com/registry/feagi-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/feagi-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan feagi-mcp --online --registry pypi

Use the free API → How scoring works

More in Learning & Documentation