mcp-typescript server on vercel

endpoint

https://langfuse.com/api/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is mcp-typescript server on vercel live?

Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.

Is mcp-typescript server on vercel free to use?

Yes — the hub reached it with no key and no payment.

What tools does mcp-typescript server on vercel have?

4 tools: getLangfuseDocsPage, searchLangfuseDocs, submitFeedback, getLangfuseOverview.

Is mcp-typescript server on vercel safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• getLangfuseOverview reads open 17h ago

  Get a high-level, machine-readable index by downloading https://langfuse.com/llms.txt. Use this at the start of a session when needed to discover key docs endpoints or to seed follow-up calls to searchLangfuseDocs or getLangfuseDocsPage. Returns the plain text contents of llms.txt. Avoid repeated calls within the same session.

  mcp-tool

  123456

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {},
    "additionalProperties": false
  }

  arguments 6 lines copy
• getLangfuseDocsPage reads unknown 17h ago

  Fetch the raw Markdown for a single Langfuse docs page. Accepts a docs path (e.g., /docs/observability/overview) or a full https://langfuse.com URL. Returns the exact Markdown (may include front matter). Use when you need a specific page content (Integration, Features, API, etc.) or code samples. Prefer searchLangfuseDocs for broader questions where there is not one specific page about it. Changelog pages (/changelog/...) are historical release notes: use them only to confirm that a feature exists or when it shipped, not as an implementation reference. Their code samples reflect the SDK/API at release time and may be outdated, so for implementation follow the current docs and the API/SDK reference instead.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "pathOrUrl"
    ],
    "properties": {
      "pathOrUrl": {
        "type": "string",
        "description": "Docs path starting with \"/\" (e.g., /docs/observability/overview) or a full URL on https://langfuse.com. Do not include anchors (#...) or queries (?foo=bar) — they will be ignored."
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• searchLangfuseDocs reads unknown 17h ago

  Semantic search (RAG) over the Langfuse documentation. Use this whenever the user asks a broader question that cannot be answered by a specific single page. Returns a concise answer synthesized from relevant docs. Prefer this before guessing. If a specific page is needed call getLangfuseDocsPage first. The raw provider response is included in _meta.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "The user's question in natural language. Include helpful context like SDK/language (e.g., Python v3, JS v4), self-hosted vs cloud, and short error messages (trim long stack traces). Keep under ~600 characters."
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• submitFeedback sends messages unknown never probed

  Submit explicit user-approved feedback to the Langfuse team. Before calling, ask permission and show the exact payload. If the user wants a reply, ask them to include their email address in the feedback text; only use an address they explicitly provide and show it in the exact payload preview. Do not include secrets, credentials, customer/project data, trace payloads, or unrelated context; the only contact detail to include is an explicitly provided reply email.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "targetType",
      "target",
      "feedback"
    ],
    "properties": {
      "goal": {
        "type": "string",
        "maxLength": 1500,
        "minLength": 1
      },
      "target": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1,
        "description": "The specific instance within targetType: the skill name, MCP tool name, CLI command, API endpoint path, or docs page path (e.g. 'queryMetrics', '/docs/mcp'). An identifier, not a sentence."
      },
      "feedback": {
        "type": "string",
        "maxLength": 3000,
        "minLength": 1
      },
      "targetType": {
        "enum": [
          "skill",
          "mcp-tool",
          "cli",
          "docs",
          "public-api",
          "other"
        ],
        "type": "string",
        "description": "Category of the thing the feedback is about."
      },
      "referenceUrl": {
        "type": "string",
        "format": "uri",
        "maxLength": 2048
      }
    },
    "additionalProperties": false
  }

  arguments 45 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.