LaborTrends NLP MCP Server

by evozim Your server? Claim it

answering

LaborTrends NLP is answering right now. Last checked 4 min ago.

Labor market trend analyzer utilizing advanced NLP semantic parsing.

Uptime history 48 days of history · worst day 99%

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

104 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

Today is the operative word: we check LaborTrends NLP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add labor-trends --transport http https://labor-trends-mcp.vercel.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "labor-trends": {
      "url": "https://labor-trends-mcp.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.labor-trends]
url = "https://labor-trends-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "labor-trends": {
      "url": "https://labor-trends-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "labor-trends": {
      "url": "https://labor-trends-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://labor-trends-mcp.vercel.app/api/mcp	sse	needs auth	100 ms	4 min ago

Alternatives to LaborTrends NLP

same job, measured the same way

Deepcontext

by wild-card

Advanced codebase indexing and semantic search MCP server

121 installs/wk local only

AI Humanizer

by evozim

Advanced text styling to preserve semantic human flow.

answering

Drop Beacon MCP

by direct-web

Search 100K+ EDC products. Track drops, compare prices, and analyze market trends.

26 installs/wk local only

VoiceIntel

by evozim

Acoustic sentiment parsing and voice veracity analyzer.

answering

mtgmon Mortgage Analytics

by lorenzopi

Read-only U.S. mortgage market, lender, GSE performance, and servicing analytics.

10 tools answering

Marketing Analytics AI MCP

by csoai-org

Marketing Analytics Ai MCP Server by MEOK AI Labs

199 installs/wk local only

FindIP

by findip

Semantic patent search & analysis: find, compare, and analyze patents by meaning.

answering

Marm MCP Server

by lyellr88

Universal MCP Server with advanced AI memory capabilities and semantic search.

1 796 installs/wk local only

LaborTrends NLP — questions

Answers built from our own checks of this server.

Why is there no tool list for LaborTrends NLP?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is LaborTrends NLP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 104 ms. The bar chart above shows every period we have measured.

How do I connect LaborTrends NLP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does LaborTrends NLP need an API key?

Yes. Every time we knock, LaborTrends NLP answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is LaborTrends NLP?

It answers our handshake in 104 ms on average, which is faster than 83% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.