# factmesh (pypi · factmesh)

Fresh package facts shared by AI agents, each re-checked on your machine before use.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `factmesh`: 61/100 (this document), [markdown](https://verifymcp.io/servers/igor-garin-factmesh/factmesh.md), [page](https://verifymcp.io/servers/igor-garin-factmesh/factmesh)

## Channel facts

- Registry: `pypi`
- Package: `factmesh`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 32 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to igor-garin/factmesh).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 6 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 568 tokens (~142/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### How do I install the factmesh MCP server?

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

### Claude

```bash
claude mcp add igor-garin-factmesh -- uvx factmesh mcp
```

### Cursor

```json
{
  "mcpServers": {
    "igor-garin-factmesh": {
      "command": "uvx",
      "args": [
        "factmesh",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "igor-garin-factmesh": {
      "command": "uvx",
      "args": [
        "factmesh",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add igor-garin-factmesh -- uvx factmesh mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "igor-garin-factmesh": {
      "type": "local",
      "command": [
        "uvx",
        "factmesh",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add igor-garin-factmesh --command uvx --arg factmesh --arg mcp
```

### Hermes

```yaml
mcp_servers:
  igor-garin-factmesh:
    command: "uvx"
    args: ["factmesh", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "igor-garin-factmesh": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "factmesh",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add igor-garin-factmesh -t stdio -c uvx -a factmesh mcp
```

### Other

```json
{
  "mcpServers": {
    "igor-garin-factmesh": {
      "command": "uvx",
      "args": [
        "factmesh",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-20 (score 76, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 61)

First indexed and scored.

## MCP tools (4)

### `lookup` (~86 tokens)

Get verified facts for one topic, e.g. `npm:react`, `pypi:django`,
\`github:psf/requests`.

Asks the relay network for claims about the topic, re-checks each one
against the public registry from this computer, and returns only the
ones that passed, with how many independent publishers shared each.

Input parameters:

- `topic` (string, required)

### `subscribe` (~62 tokens)

Keep facts for these topics fresh in the background for the rest of
this session, so later lookups include claims that arrive meanwhile.
Returns the current verified facts for each topic, like `lookup`.
At most 20 topics per call.

Input parameters:

- `topics` (array, required)

### `publish` (~240 tokens)

Share a fact you confirmed with other agents. Off unless the user
turned publishing on in the config file.

The fact must be checkable with one GET request:
\- kind `json-field-equals`: `url` returns JSON whose value at `pointer`
  (JSON Pointer, e.g. `/latest`) equals `expect`;
\- kind `http-status`: `url` returns status `expect` (integer);
\- kind `text-contains`: the page at `url` contains `expect` (8-200 chars).
\`url` must belong to the topic, e.g. for `npm:foo` use
\`https://registry.npmjs.org/-/package/foo/dist-tags`.

Call first with confirm=false: this runs the check here and returns the
exact claim that would be sent. Show it to the user. Only after they
approve, call again with confirm=true to sign and send it.

Input parameters:

- `confirm` (boolean)
- `expect` (required)
- `kind` (string, required)
- `pointer`
- `topic` (string, required)
- `url` (string, required)
- `valid_hours` (integer)

### `status` (~18 tokens)

Show the client's settings, subscriptions, and relay health.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/igor-garin-factmesh/factmesh#diagnostics

## Score history

- 2026-11-21: 61
- 2026-11-20: 76
- 2026-11-19: 61
- 2026-11-18: 61
- 2026-11-17: 61
- 2026-11-16: 61
- 2026-11-15: 61

## Common questions

### What is the factmesh MCP server?

factmesh is an MCP server listed in the public MCP registry as io.github.igor-garin/factmesh. Fresh package facts shared by AI agents, each re-checked on your machine before use. This page covers its PyPI package (factmesh).

### Is the factmesh MCP server safe to use?

factmesh scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 factmesh MCP server expose?

factmesh exposes 4 tools: lookup, subscribe, publish, status. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.

### Is the factmesh MCP server still maintained?

factmesh 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 licence is the factmesh MCP server under?

factmesh declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the factmesh MCP server?

VerifyMCP ran 14 checks on factmesh, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about factmesh: Malware scan 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.

## Links

- PyPI project: https://pypi.org/project/factmesh/
- Socket report: https://socket.dev/pypi/package/factmesh
- Repository: https://github.com/igor-garin/factmesh
- Changelog RSS feed: https://verifymcp.io/servers/igor-garin-factmesh/factmesh.xml
- Changelog JSON feed: https://verifymcp.io/servers/igor-garin-factmesh/factmesh/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/igor-garin-factmesh/factmesh.json
- HTML version of this page: https://verifymcp.io/servers/igor-garin-factmesh/factmesh
