Home › Servers › Developer Tools › pepe
pepe MCP server
pepe is Omarmhaimdat's MCP server in the official registry (io.github.omarmhaimdat/pepe). Declared transport: stdio (local, pypi), stdio (local, oci).
★ 94 GitHub stars · 2026-10-17
| Transport | stdio (local, pypi), stdio (local, oci) |
|---|---|
| Auth | No secrets declared in registry entry |
| Registry name | io.github.omarmhaimdat/pepe · 0.36.1 |
| Source | https://github.com/omarmhaimdat/pepe |
| Remote endpoints | None declared |
| Data source | Official MCP Registry |
| Kind | Community |
| GitHub stars | 94 GitHub stars, fetched 2026-10-17 |
| Date checked | 2026-10-17 |
| License | MIT |
| Last commit | 2026-10-17 |
Install
Configs are generated only from packages and remotes on the registry entry. Empty optional flags are listed instead of inserted. Nothing is added that the entry does not declare.
The registry lists this as an oci package (ghcr.io/omarmhaimdat/pepe:0.36.1) with runtime no runtimeHint, and does not include a run argument. No docker command is invented from that entry. Declared runtime arguments: --network host.
Local package (pypi)
{
"mcpServers": {
"pepe": {
"command": "uvx",
"args": [
"[email protected]",
"mcp"
]
}
}
}{
"mcpServers": {
"pepe": {
"command": "uvx",
"args": [
"[email protected]",
"mcp"
]
}
}
}{
"servers": {
"pepe": {
"type": "stdio",
"command": "uvx",
"args": [
"[email protected]",
"mcp"
]
}
}
}{
"mcpServers": {
"pepe": {
"command": "uvx",
"args": [
"[email protected]",
"mcp"
]
}
}
}claude mcp add pepe -- uvx [email protected] mcp
Optional arguments left out of the snippet
- --allow-host — Every target's host must be this host or under it (.example.com); repeat for more. Without it, a tool call may be pointed anywhere.
- --max-requests — The most requests one call may send
- --max-rate — The highest requests per second one call may ask for
- --max-concurrency — The most requests in flight at once
Other packages on the entry
- oci
ghcr.io/omarmhaimdat/pepe:0.36.1
FAQ
What transport does pepe use?
stdio (local, pypi), stdio (local, oci).
What credentials are declared for pepe?
No secrets declared in registry entry.
When was this checked, and what is the source?
These facts were checked on 2026-10-17. Registry name: io.github.omarmhaimdat/pepe. Source: https://github.com/omarmhaimdat/pepe.
Category hub: Developer Tools. Client indexes: Claude, Cursor, VS Code. This listing is in The MCP Vault until it graduates.
Similar servers
Paid placements appear first and are labelled Sponsored or Featured; the rest are sorted by GitHub stars. Sorted by GitHub stars as of 2026-10-17. Servers with no public GitHub repo follow, in alphabetical order.
Paperclip
Paperclip is Incorporatedpartners's MCP server in the official registry (io.github.IncorporatedPartners/labelhead-artist-momentum). Declared transport: Streamable HTTP (remote).
Streamable HTTP (remote)
★ 103,555 GitHub stars · 2026-10-17
Git (reference)
Reference server for reading, searching and changing local Git repositories.
stdio (local, pypi)
★ 91,330 GitHub stars · 2026-10-17
World Monitor
World Monitor is Worldmonitor's MCP server in the official registry (app.worldmonitor/mcp). Declared transport: Streamable HTTP (remote).
Streamable HTTP (remote)
★ 88,618 GitHub stars · 2026-10-17
Scrapling MCP Server
Scrapling MCP Server is D4vinci's MCP server in the official registry (io.github.D4Vinci/Scrapling). Declared transport: stdio (local, pypi), stdio (local, oci).
stdio (local, pypi), stdio (local, oci)
★ 88,274 GitHub stars · 2026-10-17
Netdata
Netdata is Netdata's MCP server in the official registry (io.github.netdata/mcp-server). Declared transport: Streamable HTTP (remote).
Streamable HTTP (remote)
★ 80,985 GitHub stars · 2026-10-17
Front-End Checklist
Front-End Checklist is Thedaviddias's MCP server in the official registry (io.github.thedaviddias/front-end-checklist). Declared transport: Streamable HTTP (remote).
Streamable HTTP (remote)
★ 74,489 GitHub stars · 2026-10-17