MCP servers › dev.parsehub › parsehub

MCP server · registry snapshot 2026-10-26 · last checked 2026-10-26

parsehub MCP server

Registry name dev.parsehub/parsehub

ParseHub.dev (documents to records) — the publisher's title

by parsehub.dev · domain (the registry's namespace rule)Source ↗Website ↗

Turn your CSV, PDF and Word files into searchable records, meeting notes and Q&A. Not parsehub.com. — the publisher's description

1 of 1 record check metversion 0.1.0streamable HTTP

Summary

dev.parsehub/parsehub is a remote MCP server listed in the official MCP registry at version 0.1.0, under the namespace of the domain parsehub.dev. Its linked repository is gitlab.com/cdobratz/mcp-server.

Record checks

1 of 1 record check met · 7 do not apply · 1 not checked

met: Registry entry is active and says how to run it
not checked: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: a secret: X-API-Key
Last tested: not tested

Tool list

Not read: It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested: no
Last tested: not tested
Latest version: 0.1.0, published 2026-10-25 (registry, as of the 2026-10-26 snapshot)
First listed version: 2026-10-25 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-26
Package and repository: checked 2026-10-26

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-24, listed on 2026-10-26 with version 0.1.0 (published 2026-10-25).

Source: the official MCP Registry list on 2026-10-24 and on 2026-10-26.

What it is

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://parsehub.dev/mcp

The entry also requires the header X-API-Key.

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "parsehub": {
      "url": "https://parsehub.dev/mcp",
      "headers": {
        "X-API-Key": "<X-API-Key>"
      }
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "parsehub": {
      "type": "http",
      "url": "https://parsehub.dev/mcp",
      "headers": {
        "X-API-Key": "${input:x-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "x-api-key",
      "description": "X-API-Key",
      "password": true
    }
  ]
}

Claude Code

claude mcp add --transport http parsehub https://parsehub.dev/mcp --header "X-API-Key: <X-API-Key>"

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "parsehub": {
      "type": "streamableHttp",
      "url": "https://parsehub.dev/mcp",
      "headers": {
        "X-API-Key": "<X-API-Key>"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "parsehub": {
      "httpUrl": "https://parsehub.dev/mcp",
      "headers": {
        "X-API-Key": "<X-API-Key>"
      }
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.parsehub]
url = "https://parsehub.dev/mcp"
http_headers = { "X-API-Key" = "<X-API-Key>" }

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "parsehub": {
      "url": "https://parsehub.dev/mcp",
      "headers": {
        "X-API-Key": "<X-API-Key>"
      }
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://parsehub.dev/mcp --transport http

Replace <X-API-Key> with your own header values; the entry marks X-API-Key as secret, so keep the file out of version control.
The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real. The command above does not send the required header (X-API-Key).

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: dev.parsehub

Repository: gitlab.com/cdobratz/mcp-server

Source: the registry entry and api.github.com · 2026-10-26.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

1 of 1 record check met · 7 do not apply · 1 not checked

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not checkedSource repository link opensThe link is not on GitHub; we only open GitHub repositories.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-26. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about dev.parsehub/parsehub

Answered from the data above

Who publishes dev.parsehub/parsehub?

The registry ties the namespace dev.parsehub to the domain parsehub.dev; only its owner can publish under it. Its linked repository is gitlab.com/cdobratz/mcp-server. These are facts from the registry and GitHub, not a rating.

Has dev.parsehub/parsehub been security tested?

No. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it. — the server's own choice

Required input the publisher declares: X-API-Key (secret).

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in a later update

listed 2026-10-26; not classified yet

Pricing modelAI-classified

pending: added in a later update

the website is not read yet

Programming language

does not apply

no existing GitHub repository (repository is hosted on gitlab, not GitHub, so this layer does not apply)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-26

MCP capability

not checked

not read (no session)

Transport

streamable HTTP

registry · 2026-10-26

Required credentials

requires a secret

registry · 2026-10-26 · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-26

Lifecycle status

active

registry · 2026-10-26

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

repository is hosted on gitlab, not GitHub, so this layer does not apply

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-10-26

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “dev.parsehub/parsehub: MCP server record.” Data checked 2026-10-26. https://protocolprobe.com/mcp/servers/dev.parsehub/parsehub

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/dev.parsehub/parsehub)](https://protocolprobe.com/mcp/servers/dev.parsehub/parsehub)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology