Data · Remote MCP server
First100
Go-to-market tools for AI agents: publish and schedule posts, find customers, SEO, outreach.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.jpalepu/first100- Version
- 2.2.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-15
- Updated
- 2026-09-15
- Publisher
- jpalepu (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/jpalepu) · how
- Website
- firsthundred.app
- Repository
- github.com/jpalepu/first100
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://firsthundred.app/api/mcp | Authorization (required, secret) |
| Streamable HTTP | https://firsthundred.app/api/mcp/core | Authorization (required, secret) |
| Streamable HTTP | https://firsthundred.app/api/mcp/seo | Authorization (required, secret) |
| Streamable HTTP | https://firsthundred.app/api/mcp/outreach | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://firsthundred.app/api/mcp(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://firsthundred.app/api/mcp/core(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://firsthundred.app/api/mcp/seo(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://firsthundred.app/api/mcp/outreach(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | first100-mcp | 2.2.0 | stdio |
How to connect First100
First100 is a remote MCP server: there is nothing to install. Its endpoints are https://firsthundred.app/api/mcp, https://firsthundred.app/api/mcp/core, https://firsthundred.app/api/mcp/seo and https://firsthundred.app/api/mcp/outreach, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: first100-mcp version 2.2.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y first100-mcp@2.2.0. It reads the environment variable FIRST100_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"first100": {
"command": "npx",
"args": [
"-y",
"first100-mcp@2.2.0"
],
"env": {
"FIRST100_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Firmfold: Company Enrichment APIFirmfold: company enrichment by domain/email/name: logo, tech, contacts, jobs, firmographics. | Remote · HTTPLive check: sign-in required |
| Firmfold: Company Enrichment APIFirmfold: company enrichment by domain/email/name: logo, tech, contacts, jobs, firmographics. | Remote · HTTPLive check: sign-in required |
| FirmTape Geo - public records of world eventsGeopolitical OSINT: sanctions, NOTAMs, maritime warnings, outages, conflict records with sources. | Remote · HTTPLive check: ✓ handshake |
| FirmTroveSearch, count and export Dutch companies from your AI agent. | Remote · HTTPLive check: sign-in required |
| FirstDataHosted MCP server for finding authoritative primary data sources and official portals. | Remote · HTTPLive check: sign-in required |
| fish-bridge - Session Knowledge GraphCompresses AI chat sessions into a typed knowledge graph. Local/offline via Ollama. | Local · stdio |
| Fitness AI ConnectorGarmin data in Claude & ChatGPT via the Garmin Health API. OAuth sign-in, no password sharing. | Remote · HTTPLive check: sign-in required |
| FITsocietyAccess approved FITsociety clients, schedules, bookings and coaching data with AI assistants. | Remote · HTTPLive check: sign-in required |