Add Tapline remote MCP server
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 35/100
Línea de trabajo
The draft entry is already on the submitter’s add-tapline-remote branch, with files under registries/{toolhive,official}/servers/tapline-remote/ and an icon.svg. Review the registry inclusion criteria for proprietary services and check the entry against the Tapline server details and official-vendor exception; the submitter says catalog validate, catalog build, and go test ./... pass. Done means maintainers approve inclusion and the entry passes the catalog checks.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
MCP Server Information
Server Name: Tapline (Remote)
Repository URL: https://github.com/TaplineData/tapline-mcp
Brief Description: Structured JSON from YouTube, Airbnb, TikTok, Instagram, Facebook, LinkedIn, Zillow and Google Maps.
Tapline is a first-party hosted MCP server, published by Tapline (the vendor of the service). It asks for the official-vendor exception in the inclusion criteria: the backend is proprietary. The linked repository (MIT) holds the docs, client configs, icon and the Official MCP Registry server.json (sh.tapline/tapline).
| Field | Value |
|---|---|
| Endpoint | https://api.tapline.sh/mcp (Streamable HTTP) |
| Auth | OAuth 2.1 with Dynamic Client Registration, or an API key as Authorization: Bearer |
| Tools | search_endpoints, get_endpoint, call_endpoint, read_more (all read-only) |
| Docs | https://tapline.sh/docs/mcp |
| Cost | A Tapline account is needed. 100 free credits on sign-up; failed requests are not charged. |
Workflow: an agent calls search_endpoints with "google maps places search", reads the parameters with get_endpoint, then call_endpoint returns the places as JSON. The same flow covers YouTube transcripts, LinkedIn jobs, Airbnb listings, Zillow property records and the other sources.
Basic Requirements
- Open Source: Uses acceptable license (Apache-2.0, MIT, BSD-2-Clause, BSD-3-Clause or other permissive license) — the repository is MIT; the hosted server is proprietary (official-vendor exception, see above)
- MCP Compliant: Implements MCP API specification
- Active Development: Recent commits and maintained
- Documentation: Basic README and setup instructions
- Security Contact: Method for reporting security issues (SECURITY.md)
Submitter Checklist
- I have read the MCP Server Registry Inclusion Heuristics
- This server meets the basic requirements listed above
- I understand this will undergo automated and manual review based on Registry Management
A draft entry (registries/{toolhive,official}/servers/tapline-remote/, with icon.svg) is ready on bibbycodes:add-tapline-remote. catalog validate, catalog build and go test ./... pass locally. I will open the PR after approval.
I work on Tapline.
🤖 Generated with Claude Code
- Lenguaje dominante
- Go
- Estrellas
- 26
- Forks
- 104
- Merge medio
- 1 d 10 h
- PR fusionados (30 d)
- 88
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de stacklok/toolhive-catalog
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
stacklok/toolhive-catalog#2024 ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
stacklok/toolhive-catalog#1986 ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
stacklok/toolhive-catalog#1976 ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
stacklok/toolhive-catalog#1969 ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
stacklok/toolhive-catalog#1968 ·
Los mantenedores suelen responder en 1 día
Todos los issues de stacklok/toolhive-catalog
Issues similares
-
HTTP probe loses insecureSkipVerify in the generated probe manifestPosiblemente ocupada @BahaaMattar la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 87/100
litmuschaos/litmus#5745 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 2 días
-
type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
Los mantenedores suelen responder en 1 día
-
messaging/v1: IsGRPCProtocol and InternalMetadataToGrpcMetadata panic on empty or nil metadata valuesPosiblemente ocupada @patelshivani2283-lab la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
Los mantenedores suelen responder en 1 día