Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

AIFeed

by denyn1version 1.0.0-draft.2i★ –iRuns on your computer
Registry nameio.github.denyn1/aifeed-mcp-server

Install

Overview

Description from the maker (original English)

Verify signed AIFeed permissions, fetch token-budgeted markdown, and verify assets for AI agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "aifeed": {
      "command": "npx",
      "args": [
        "-y",
        "aifeed-mcp-server"
      ]
    }
  }
}

Run this in your terminal

claude mcp add aifeed -- npx -y aifeed-mcp-server

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "aifeed": {
      "command": "npx",
      "args": [
        "-y",
        "aifeed-mcp-server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "aifeed": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "aifeed-mcp-server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account denyn1, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

  • More stars than 0% of the other 3527 servers in this category
  • Published to the registry more recently than 41% of the other 3527 servers in this category
  • Basic checks equal to or better than 100% of the other 3527 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is AIFeed safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0-draft.2) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago
Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 7 days ago
Install

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 4 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

AIFeed

English · Bahasa Indonesia · 中文

Signed content permissions for the AI web.

Declare, sign, and revoke what AI agents may do with your content — and let agents prove it.

▶ Watch: How AIFeed stops web scraping waste

Website · Protocol flow · Benchmark · Complete guide · Paper (PDF)


1-Minute Quickstart

Publisher side — sign what agents may do with your content:

npx aifeed keygen --out .aifeed                         # Ed25519 key pair

npx aifeed site build ./public --domain example.com \ --key .aifeed/aifeed-private.pem --llms --inject # manifest + page markdown + index npx aifeed validate ./public --domain example.com # verify locally

Prefer zero config? npx aifeed init --domain example.com --dir ./site creates the keys, a signed manifest, and the DNS/host setup guide in one step.

Agent side — verify any domain in 3 lines:

npm install @aifeed/verify
const { verifyRemote } = require('@aifeed/verify');

const out = await verifyRemote('example.com'); // discovery → signature → DNS anchor console.log(out.result, out.anchor.status); // VERIFIED anchored

TypeScript: import { verifyRemote } from '@aifeed/verify';

Where to go next: Why AIFeed? · agent quickstart · publisher AI guide · Studio publisher app · npm: aifeed CLI · @aifeed/verify

Why AIFeed?

AI agents now drive a large and growing share of web traffic, but the signals that say what they may do are unsigned text files. Anyone can edit them, nothing binds them to a domain, and there is no way to revoke them. The asymmetry is measurable:

  • 1.9 billion crawls ignored robots.txt rules in a single half-year (one vendor).
  • A 70,900 : 1 crawl-to-referral ratio was measured for a major AI provider.
  • AI bots averaged 4.2 % of HTML requests in 2025, peaking at 6.4 %.

AIFeed replaces "please respect this file" with a cryptographically verifiable declaration, plus lean agent-ready content that cuts cost on both sides.

How it works

  1. Generate an Ed25519 key pair — the private key never leaves the origin.
  2. Publish a signed manifest at /.well-known/ai.json: per-use permissions (training, retrieval, quote, …), crawl limits, license, revision.
  3. Anchor the key in DNS (_aifeed TXT) so a manifest cannot be spoofed by another domain.
  4. Agents verify the chain — TLS → domain → signature (JCS + Ed25519) → DNS anchor — and re-check a multi-signature revocation registry on every use.
  5. Rotate keys safely — announce the successor with an old-key-signed directive (plus an advisory DNS pk2 cross-check), keep a bounded overlap, cut over, then revoke the old key permanently. Runbook: docs/rotation.md.
  6. Serve lean content under one of two profiles (below), with a signed delta index so unchanged pages cost 0 bytes.

For AI agents: the check-first guide (discovery → verification → permission decisions → delta → failure handling) is in docs/agent-quickstart.md, with a runnable example at examples/agent/compliant-agent.js.

Verify from other stacks

Independent Python package (standard library only):

pip install aifeed
from aifeed import verify

report = verify.verify_directory('./my-site', domain='example.com') print(report['result'], report['errors'])

Prefer the repository? The same CLI is here (zero dependencies, Node ≥ 20):

cd aifeed-protocol

node bin/cli.js keygen --out keys/ node bin/cli.js validate https://example.com node bin/cli.js site build ./public --domain example.com --key keys/aifeed-private.pem

Two content profiles

ProfileMedia typeExtensionNotes
AIFeed Markdown (native)text/aifeed+markdown.aifeed.mdIn-band signed policy block, token budget, translation alternates, triage metadata
MAKO (compatibility)text/mako+markdown.mako.mdExternal MAKO trust profile, served from the same signed bytes with its own signature context

Dual-stack origins serve both; cross-format replay is rejected by design.

Measured results

All numbers are reproducible from committed artifacts (npm run bench:mako, npm run bench:enforcement); the test environment is a single machine on loopback networking with a synthetic 60-page corpus. Honest baseline included.

WhatResultLabel
Conversion to markdown profiles vs HTML−68.83 % transferred bytesmeasured
Delta consumption (10 % pages changed)−95.73 % vs HTML crawlmeasured
Publisher egress bytes / CPU / peak connections−55.19 % / −56.23 % / −88.24 %measured (simulation)
AI-side received bytes (all profiles / compliant client)−54.84 % / −72.93 %measured (simulation)
Unchanged pages skipped14 of 18measured (simulation)
Signature verification cost0.70 ms / pagemeasured

The 30-day live pilot has not run yet; projections per 1,000 tenants are labeled as model extrapolations, and vendor claims of up to 94 % token reduction require semantic summarization this project does not perform automatically.

What's in this repository

PathContents
lib/ + bin/Zero-dependency reference implementation and CLI
packages/ + clients/python/Published packages: CLI (aifeed), SDK (@aifeed/verify), MCP server, build plugins (@aifeed/frameworks), PyPI aifeed verifier
conformance/Conformance vectors: 34 manifest · 39 MAKO · 11 AIFeed Markdown
wp-plugin/WordPress plugin: signed manifest, AIFeed Markdown + MAKO dual-stack, /llms.txt
spec/Specifications EN/ID: manifest v0.1/v0.2, AIFeed Markdown v1.0
schema/JSON Schemas for manifests, signatures, AIFeed Markdown, MAKO
paper/Preprint: LaTeX source, PDF, claim ledger, arXiv bundle
docs/Agent quickstart, deploy and namespace guides, Indonesian project notes
studio/Zero-dependency local publisher app: crawl, declare, build, verify, export, and rotate
docs/REFERENCE.mdReference implementation details, what gets verified, CLI quickstart

Documentation

  • Specifications: spec/en · spec/id · schemas
  • Reference implementation: docs/REFERENCE.md
  • Maintenance contract (AI agents & devs): AGENTS.md
  • Architecture: docs/architecture.md · Release guide: docs/release.md
  • Agent quickstart (client side): docs/agent-quickstart.md
  • Publisher AI guide (owner side): docs/publisher-ai-guide.md
  • Publisher Studio (local app): studio/README.md
  • Agent skill: skills/aifeed/SKILL.md (installable via ClawHub: npx clawhub install aifeed)
  • Complete guide: docs/penjelasan-aifeed.html (source of https://aifeed.md/penjelasan.html)
  • Security policy: SECURITY.md
  • Governance & open-core policy: GOVERNANCE.md
  • Deploying the site: docs/deploy-site.md
  • arXiv submission notes: paper/ARXIV-SUBMISSION.md

Status

  • Release `1.0.0-draft` — the specifications are not frozen yet. Wire versions: manifest 0.1/0.2, AIFeed Markdown 1.0, MAKO 0.2.
  • Conformance: 34 manifest + 39 MAKO + 11 AIFeed Markdown vectors, executed by independent JavaScript and Python verifiers, plus PHP differential fixtures, 90,000+ fuzz executions, and a WordPress end-to-end test.
  • Not claimed: external cryptographic review and a live pilot (both pending); origin+DNS compromise is undetectable on first contact.

License and contact

Specifications CC BY 4.0 · reference code and plugin MIT · vectors CC0. Contact: — security reports per SECURITY.md.

Ask PopNx