Skip to main content

Machine Internet

Turn any website into an MCP server. No API needed.

uvx machine-internet wrap https://bundlephobia.com/package/react

Machine Internet opens the site in a headless browser, watches the hidden API calls the page makes, and turns them into a small set of clean tools that Claude, Cursor or any MCP client can call directly.

Demo: wrapping bundlephobia.com and calling the new tool

CI License Python MCP


Try it in 30 seconds (no API key)

Ten sites come pre-wrapped, most with no public API. Add one to your Claude Desktop or Cursor config:

{
  "mcpServers": {
    "bundlephobia": {
      "command": "uvx",
      "args": ["machine-internet", "serve", "bundlephobia"]
    }
  }
}

Restart your client and ask: "How big is react-dom gzipped, and is lodash-es tree-shakeable?"

Example Site Tools
bundlephobia bundlephobia.com 6: package size, tree-shaking check, size history, similar packages, per-export sizes, recent
caniuse caniuse.com 4: search features, browser support data, feature details, news
npm_trends npmtrends.com 4: package info, weekly downloads, download trends, GitHub stats
deps_dev deps.dev 7: versions, dependencies, dependency graph, dependents, requirements, stats
crates_io crates.io 6: search crates, crate info, versions, version details, stats, summary
huggingface huggingface.co 1: search models, datasets and Spaces
hacker_news hn.algolia.com 1: full-text search of HN stories and comments
archive_org archive.org 3: search the archive, item metadata, item favorites
ossinsight ossinsight.io 2: search GitHub repos, users and orgs, live GitHub event stats
regex101 regex101.com 3: browse the community library, get a saved regex, list versions

You need uv for uvx. Or install it once with pip install machine-internet (or straight from GitHub: pip install git+https://github.com/chetanty/machine_internet) and use machine-internet as the command.

Hosted, nothing to install: every example is also live at machine-internet.vercel.app as a remote MCP endpoint, e.g. https://machine-internet.vercel.app/mcp/bundlephobia. Clients with remote MCP support take the URL directly; others can use npx mcp-remote <url>. Some sites rate-limit requests from cloud servers (npm's download stats do), so for heavy use run serve locally, which calls the site from your own connection.


Wrap your own site

Set an LLM key (any one of these works):

export ANTHROPIC_API_KEY=...   # or OPENAI_API_KEY, or GEMINI_API_KEY

Then point it at a page that loads data as you use it:

uvx machine-internet wrap https://bundlephobia.com/package/react
Wrapping https://bundlephobia.com/package/react
  Checking for an OpenAPI spec ...
  Sniffing network traffic in a headless browser ...
  [OK] Inferred 4 endpoints
  Condensing into agent tools ...
  [OK] 4 tools:
       get_package_size: Use this tool to get detailed size information for a JavaScript packag
       get_package_history: Use this tool to retrieve the historical versions of a specific JavaSc
       ...

Add this to your MCP client config (Claude Desktop, Cursor, ...):
{ "mcpServers": { "bundlephobia_api": { "command": "uvx", "args": ["machine-internet", "serve", "bundlephobia_api"] } } }

The first run downloads headless Chromium once (about 150 MB). Wrapping takes 1 to 3 minutes and costs a few cents of LLM usage. Serving afterwards needs no LLM at all.

Tips

  • Pick a page that fetches data: a search results page or an item page works better than a static landing page.
  • If the site publishes an OpenAPI spec, it is used automatically and nothing is sniffed. Point at one directly with --spec <url>.
  • Large specs: keep only some areas with --tags repos,issues.

How it works

  1. Spec check. Probes about 20 standard locations (/openapi.json, /swagger.json, ...). If a real spec exists, it is parsed directly.
  2. Traffic sniffing. Otherwise, launches headless Chromium, loads the page, scrolls and clicks through it, and records every same-site JSON request. Analytics and ad trackers are filtered out.
  3. Inference. An LLM reads the captured requests and responses and infers each endpoint's path, parameters and types.
  4. Condensation. An LLM collapses the endpoints into at most 15 verb_noun tools, with descriptions written so an agent knows when to use each one.
  5. Serving. The result is a small JSON file. machine-internet serve exposes it as a standard MCP server (stdio by default, SSE with --sse) that makes real calls to the real site.

Commands

machine-internet wrap <url> [--name NAME] [--spec URL] [--tags a,b] [--sniff] [-o FILE]
machine-internet serve <name-or-file.json> [--sse --port 8000]
machine-internet list                  # bundled examples and servers you have wrapped
machine-internet tools <name>          # show a server's tools and parameters
machine-internet call <name> <tool> key=value ...   # call a tool from the terminal
machine-internet config <name>         # print the MCP client config block

Wrapped servers are saved to ~/.machine-internet/schemas/.

APIs that need auth: credentials are read from the environment when the server runs: MI_TOKEN (bearer), MI_API_KEY (plus MI_API_KEY_NAME, MI_API_KEY_IN=header|query), MI_USERNAME / MI_PASSWORD, or MI_TOKEN_URL / MI_CLIENT_ID / MI_CLIENT_SECRET for OAuth2 client credentials. Put them in the env block of your MCP client config.


What it works on

It works on sites whose pages load their data with API calls from the browser: most single-page apps, search pages, dashboards and developer tools. It does not work on sites that render pages on the server, or that block headless browsers.

Results from pointing wrap at 15 popular sites, with each generated tool then called for real:

Result Sites
Works crates.io, deps.dev, Hugging Face, archive.org, HN Search (Algolia), OSS Insight
Partly works Open Library (1 of 2 tools)
No hidden API found (server-rendered) IMDb, Reddit, GitHub Trending, npmjs.com
Blocked or only trackers seen Product Hunt, lichess, packagephobia
Nothing useful captured dev.to (only a session-token call)

So roughly half of the arbitrary sites tried. When it fails, it says why and suggests a page that is more likely to work.

Limitations

  • Internal APIs change without notice. A wrapped site can break when it ships a new frontend. Re-run wrap to refresh it.
  • It only sees what the page does while loading and being clicked. Actions behind logins, multi-step forms or heavy anti-bot protection usually are not captured.
  • LLM output varies. If the tools look wrong, run wrap again or narrow the page you point it at.

Use responsibly

Undocumented APIs are still someone else's service. Check the site's terms before wrapping it, keep request volume reasonable, and do not use this to get around access controls or rate limits.


How it compares

Machine Internet OpenAPI-to-MCP converters Browser agents
Works without an API spec Yes No Yes
Agent calls the API directly (fast, cheap per call) Yes Yes No, drives a browser every time
One command from URL to MCP server Yes Needs a spec No

Related work worth knowing: Integuru generates integration code from captured traffic, and mitmproxy2swagger builds OpenAPI specs from recorded traffic. Machine Internet's focus is going straight from a URL to a running MCP server.


Development

git clone https://github.com/chetanty/machine_internet
cd machine_internet
pip install -e ".[dev]"
pytest
python evals/score.py      # condensation quality evals (needs an LLM key)

License

Apache 2.0

Metadata

Release files for machine-internet 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for machine-internet 0.1.0
File Size Uploaded Provenance Actions
machine_internet-0.1.0.tar.gz 39.0 kB With provenance Details for machine_internet-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for machine-internet 0.1.0
File Interpreter ABI Platform Actions
machine_internet-0.1.0-py3-none-any.whl Python 3 none any Details for machine_internet-0.1.0-py3-none-any.whl

Total release size: 90.3 kB

Release files / machine_internet-0.1.0.tar.gz

Download URL machine_internet-0.1.0.tar.gz
Size 39.0 kB
Tags Source
SHA-256 checksum
How to use checksums
f268b93f0f8d43a9849b1ca2599ad6c3e9ff58799699a3d653db2695918a8892
BLAKE2b-256 checksum
How to use checksums
d69ac39ee3264167b5a5854d96535f21e30c1b4e49ca689f35a6e150e4c1bef4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.

Transparency log

Release files / machine_internet-0.1.0-py3-none-any.whl

Download URL machine_internet-0.1.0-py3-none-any.whl
Size 51.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
991f2b99738638e7d254b377e9107d415ff4148112c5a1120d3eb3b021744891
BLAKE2b-256 checksum
How to use checksums
7d88e5dadb5083e8ca1c236db7e153f8aae94b7e43818c4b7d3ba2c2e076bf73
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.

Transparency log

Security for machine-internet 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for machine_internet-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page