Catalogue research · Source status

MCP server source status

A dated inventory of 26 MCP profiles in iThub, with repository flags and source links. This dataset describes their recorded sources, not a performance ranking or a security assessment.

Download the snapshot (JSON)Browse MCP servers →Read the method ↓

What this snapshot shows

Catalogue checked . Snapshot edited . The 12 distinct GitHub repositories are checked once each; several profiles share the same reference repository.

Archived repository
7
Explicit maintenance notice
1
Repository not archived
15
Provider documentation
3

“Repository not archived” means GitHub returned archived: false. It does not establish active maintenance, support, reliability or compatibility. A provider-documentation entry has no repository archive flag in this snapshot.

Profile and source inventory

The source check date belongs to the evidence shown in that row. On a small screen, scroll the table horizontally to see each source.

26 published MCP server profiles, sorted by name
ProfileRecorded statusSourceChecked (UTC)
Firecrawl MCP ServerBrowser and webRepository not archivedMaintenance not assessedfirecrawl/firecrawl-mcp-server ↗GitHub metadata ↗
MCP AWS ServerDeveloper platformsRepository not archivedMaintenance not assessedawslabs/mcp ↗GitHub metadata ↗
MCP Brave Search ServerBrowser and webArchived repositorymodelcontextprotocol/servers-archived ↗GitHub metadata ↗
MCP Cloudflare ServerDeveloper platformsRepository not archivedMaintenance not assessedcloudflare/mcp-server-cloudflare ↗GitHub metadata ↗
MCP Docker ServerDeveloper platformsRepository not archivedMaintenance not assessedckreiling/mcp-server-docker ↗GitHub metadata ↗
MCP Everything ServerDeveloper platformsRepository not archivedMaintenance not assessedmodelcontextprotocol/servers ↗GitHub metadata ↗
MCP Fetch ServerBrowser and webRepository not archivedMaintenance not assessedmodelcontextprotocol/servers ↗GitHub metadata ↗
MCP Filesystem ServerKnowledge and documentsRepository not archivedMaintenance not assessedmodelcontextprotocol/servers ↗GitHub metadata ↗
MCP Git ServerDeveloper platformsRepository not archivedMaintenance not assessedmodelcontextprotocol/servers ↗GitHub metadata ↗
MCP GitHub ServerDeveloper platformsArchived repositorymodelcontextprotocol/servers-archived ↗GitHub metadata ↗
MCP Google Drive ServerKnowledge and documentsArchived repositorymodelcontextprotocol/servers-archived ↗GitHub metadata ↗
MCP Jira ServerDeveloper platformsRepository not archivedMaintenance not assessedsooperset/mcp-atlassian ↗GitHub metadata ↗
MCP Linear ServerDeveloper platformsProvider documentationService availability not testedlinear.app ↗
MCP Memory ServerKnowledge and documentsRepository not archivedMaintenance not assessedmodelcontextprotocol/servers ↗GitHub metadata ↗
MCP Notion ServerKnowledge and documentsNot actively maintainedmakenotion/notion-mcp-server ↗
MCP Obsidian ServerKnowledge and documentsRepository not archivedMaintenance not assessedMarkusPfundstein/mcp-obsidian ↗GitHub metadata ↗
MCP Playwright ServerBrowser and webRepository not archivedMaintenance not assessedmicrosoft/playwright-mcp ↗GitHub metadata ↗
MCP PostgreSQL ServerDatabasesArchived repositorymodelcontextprotocol/servers-archived ↗GitHub metadata ↗
MCP Puppeteer ServerBrowser and webArchived repositorymodelcontextprotocol/servers-archived ↗GitHub metadata ↗
MCP Sentry ServerDeveloper platformsRepository not archivedMaintenance not assessedgetsentry/sentry-mcp ↗GitHub metadata ↗
MCP Sequential Thinking ServerKnowledge and documentsRepository not archivedMaintenance not assessedmodelcontextprotocol/servers ↗GitHub metadata ↗
MCP Slack ServerKnowledge and documentsArchived repositorymodelcontextprotocol/servers-archived ↗GitHub metadata ↗
MCP SQLite ServerDatabasesArchived repositorymodelcontextprotocol/servers-archived ↗GitHub metadata ↗
MCP Vercel ServerDeveloper platformsProvider documentationService availability not testedvercel.com ↗
mcp-server-kubernetesDeveloper platformsRepository not archivedMaintenance not assessedFlux159/mcp-server-kubernetes ↗GitHub metadata ↗
mcp-server-stripeDeveloper platformsProvider documentationService availability not testeddocs.stripe.com ↗

Method, scope and reuse

  1. Catalogue boundary. Include published listings whose CMS type is mcp-server at the recorded inventory check. OpenSEO and other tools with a different type are excluded. This is the iThub catalogue, not a census of every MCP server.
  2. Source identity. Use the source recorded in the editorial profile. Historical reference implementations point to their archived repository; hosted integrations point to provider documentation. A migrated repository must match the reviewed identity before the snapshot can be refreshed.
  3. Repository evidence. Request each unique GitHub repository once through its public metadata API and retain the returned archive flag and response-check timestamp. If a check fails, keep a previously verified fact with its original date; never turn a failed request into a fresh verification.
  4. Maintenance notices. “Not actively maintained” is an explicit notice recorded from the linked project source during editorial review. It is not inferred from commit frequency or the absence of a release. Archive status takes precedence when a repository is archived.
  5. Hosted sources. Check that the provider documentation responds. This does not exercise OAuth, a live MCP endpoint, paid functionality or service uptime.

The download contains the exact rows, repository metadata, check dates and catalogue query used here. Dates and counts belong to this snapshot; refreshes preserve its first-publication date. Cite the page title, snapshot edit date and individual source-check dates when reusing a result.

Functional checks are a separate form of evidence. Read how iThub records executed tests, or report a source correction.