Particles runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 13 Sep 2026.
An append-only ledger of sourced, dated, confidence-scored claims your agent cites and you audit
We read the source, 21 h ago · rules 3dff92dd89df
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
return subprocess.run(["git", *args], capture_output=True, text=True, check=True).stdout.strip()
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check Particles every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add particles -- uvx linkedparticles
{
"mcpServers": {
"particles": {
"args": [
"linkedparticles"
],
"command": "uvx"
}
}
}
[mcp_servers.particles]
command = "uvx"
args = ["linkedparticles"]
{
"mcpServers": {
"particles": {
"args": [
"linkedparticles"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"particles": {
"args": [
"linkedparticles"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
ANTHROPIC_API_KEY (Anthropic API key. Required for the tools that call a model — `query` composes a cited natural-language answer, and the semantic half of `lint` reasons over claim pairs. The accessors that only read the store (`particle_show`, `particles_list`, `subjects_*`, `events_*`, `graph_view`, `quality_report`) work without it.), DATABASE_URL (SQLAlchemy URL of the belief store to serve. Defaults to `sqlite+aiosqlite:///./particles.db` in the working directory.), PARTICLES_CONFIG (Path to a `config.yaml` holding the rest of the engine's settings — additional stores, model selection per purpose, and the `mcp.write.enabled_stores` allowlist that turns the write tools on.).
The author declared them in the registry entry; get the values from the project itself.
The agent switchboard: identity, policy, loop-guard, and an append-only audit ledger.
Scan, enumerate, and risk-score every MCP server configured on your machine.
Parse a document into structured, confidence-scored fields. Bring your own model, pay per scan.
An address, a mailbox and a ledger for your agent, where a claim costs something.
Plan, schedule and generate SEO articles on a content calendar, from your agent.
An app builder for agents. Your agent creates screens, a Postgres database, and a live URL.
Open, sourced, confidence-scored intelligence on AI startups - a free PitchBook alternative.
Read-only MCP access to a local append-only evidence ledger for AI agent sessions.
Answers built from our own checks of this server.