Particles
An append-only ledger of sourced, dated, confidence-scored claims your agent cites and you audit
The current version, v1.224.6, was published to the official MCP registry on 2026-11-01. It is distributed as linkedparticles on PyPI, filed under Other by this index, and declares 3 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using Particles in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“Tool logs claims, no hidden instructions”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-11-05).
Contracts can change after screening, with no version bump. The gate pins Particles’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for Particles](https://mcpindex.ai/server/org-linkedparticles-particles) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/org-linkedparticles-particles">Independent trust record for Particles</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/org-linkedparticles-particles)<a href="https://mcpindex.ai/server/org-linkedparticles-particles"><img src="https://mcpindex.ai/api/v1/badge/org-linkedparticles-particles" alt="mcpindex verdict" height="20" /></a>ANTHROPIC_API_KEYAnthropic 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_URLSQLAlchemy URL of the belief store to serve, used as given, so write a SQLite path absolute: a relative one opens against the directory the server starts in. Without it, and without PARTICLES_CONFIG, the server serves the store `~/.particles/config.yaml` names (a relative path there is read under `~/.particles/`), or `~/.particles/particles.db` when that file names none, never a store in the directory it starts in.
PARTICLES_CONFIGPath to the config file holding the rest of the server's settings: additional stores, model selection per purpose, and the `mcp.write.enabled_stores` allowlist that turns the write tools on. This is the supported way to give the server settings. Without it the server reads `~/.particles/config.yaml`, never a `config.yaml` in the directory it starts in. Give it as an absolute path: a relative one is refused. When you set it, also set `DATABASE_URL` to an absolute path or name one as `storage.database_url` in the file: a server started with a config file refuses a store path relative to its working directory, and refuses to start while any store under `storage.stores` has one.
Bulk-launch and manage ads across many Meta, TikTok and Snapchat ad accounts for agencies.
Confidential VMs (Intel TDX) by the hour, paid in USDC over x402: live plans, prices, how to buy.
Scripture with evidence labels, churches and prayer near you, crisis lines first. Jesus is Lord.