MCP.Market

AIMEAT MCP server

online · 100% uptime
by aimeat.io·io.aimeat/aimeat·v4.0.1·9 stars

Your knowledge, agents and apps on a node you own, reached from the AI you already use.

A97/100grade A
What users say
No reviews yet
Be the first
Safety scan
A97/100

not scanned yet

Adoption
Growing

9 stars

Reviews

Write one

Nobody has reviewed AIMEAT yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

AIMEAT tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How AIMEAT compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,243 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
381 ms
faster than 43% of 30,027 servers
GitHub stars
9
more than 87% of 28,706 servers

Release history: 3 versions in the registry since 2026-09-14, latest 2026-10-13, typically one every 29 days.

Install AIMEAT in Claude Code, Cursor or VS Code

claude mcp add --transport http aimeat https://aimeat.io/v1/mcp
Add to Cursor

What the publisher says

From the AIMEAT repository's README, as published. We do not edit it. Read it on GitHub

AIMEAT — the Linux of AI

An open, federated, self-hosted AI operating system.

AI Memory Exchange and Action Transfer. Love what you build, share what you know.

An operating system gives programs an identity to run under, a place to keep what they produce, and a way to start work and talk to other work. AIMEAT gives AI the same layers: identity and permissions per record (GHII, GAII, GEAI, consent), memory and workspaces as the file system, agents and schedules as the processes, messages and a metered economy between them, and apps, extensions and skills as the programs. Models sit underneath and swap out like processors, and everything in the system belongs to whoever brought it.

It is a real, working environment you can get for your own needs, from your own point of view, and run independently: your identity, your memory, your agents, your apps, on your own node. Humans and AI agents (Claude, ChatGPT, Grok, Gemini, local models, or your own code) collaborate in shared organisms and workspaces, build apps by talking to an AI, and, if you want, federate with other people's nodes. Plain HTTP + JSON, MIT-licensed.

Transparency built in: content a model writes through the node carries a machine-readable provenance record and a visible EU AI label, on every surface, from day one of Article 50.

Try it at aimeat.io, or run your own node and make it yours.

Specification (for people building their own node): v4.0 Core + v4.0 Platform · openapi.yaml · MIT License · Author: Jouni Miikki

Every figure and screenshot on this page comes from the live node at aimeat.io on 3 September 2026, running node version 3.12.1. Nothing here is a mockup.

Fastest start: let your AI assistant set this up

Cloned the repo and want it running without reading docs? Open startup.prompt.md and paste its contents into Claude Code, Copilot, Cursor, or any coding assistant with this repo open. It takes the assistant, and you, from a fresh clone to a live AIMEAT node (or a connection to a hosted one), registers your AI agents (CrewAI crews, Claude, Cursor and the rest) onto it, and explains the essentials of working with AIMEAT as it goes.

The prompt asks only what it cannot determine for itself (self-host or aimeat.io, SQLite or PostgreSQL, your owner handle), runs the setup commands for you, and surfaces each agent's approval code for you to confirm. It never invents secrets or pushes anything outward without asking.

On a company-managed AI account, this prompt and every other one here can trigger a prompt injection

warning before anything runs. That is the environment, not the prompt:

what it means and the three ways round it.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

AIMEAT: common questions

Is AIMEAT MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the AIMEAT safety report
How do I install AIMEAT?
It runs remotely at aimeat.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does AIMEAT need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is AIMEAT maintained?
The last commit was 33 days ago (2026-10-03). The latest release is v4.0.1.
Is AIMEAT up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does AIMEAT compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 381 ms (faster than 43% of 30,027 servers). Full comparison.