pkulaw-mcp
Related Servers
Alternatives to pkulaw-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and agents to search a legal document collection via hybrid BM25+dense retrieval, read articles with context, and generate full or short citations. It also exposes whole acts as Markdown resources, provides a citation-answering prompt, and supports stdio and streamable HTTP transports.MIT
- AlicenseAqualityCmaintenanceEnables AI clients to search and retrieve official legal documents from the Ministry of Government Legislation's Open API — current and historical statutes, administrative rules, local ordinances, court precedents, constitutional decisions, and legal interpretations — including article-level text lookup. Runs locally over stdio with paginated retrieval of long responses and no external database or web UI required.3MIT
- AlicenseAqualityBmaintenanceEnables natural language search and retrieval of Korean laws, precedents, administrative rules, and legal terms, with deep legal chain analysis and full-text access. Supports stdio and streamable-http transports for local and remote deployment.10MIT

@shieldlabs-ai/mcpofficial
AlicenseAqualityAmaintenanceEnables AI assistants to read identification verdicts, search history, summarize entities, explain risk scores, and verify webhook signatures through read-only tools over stdio or streamable HTTP.615 npmMIT- AlicenseNot gradedqualityBmaintenanceProvides LLM clients with market intelligence tools over stdio, including market snapshots, price history, sentiment scoring, evidence search, and research briefs, with saved-run resource access.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run eight data tools over stdio for product search, ad transparency, company intent, job/ATS lookup, keyword volume, domain SEO, and YouTube transcripts, returning JSON envelopes with item limits, truncation metadata, and structured errors.37 PyPIMIT
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: one discovers upstream tool names and schemas, the other invokes them. The descriptions explicitly clarify the relationship and prevent confusion between listing and calling.
Both names use a consistent pkulaw_ prefix and verb_noun structure (list_upstream_tools, call_upstream_tool). There is a minor singular/plural mismatch between 'tools' and 'tool', but the pattern remains predictable.
Two meta-tools are appropriate for a gateway/proxy server whose real surface is discovered dynamically. The count is slightly below the typical 3-15 range, but each tool earns its place and avoids unnecessary duplication.
The list-and-call pair covers the core proxy lifecycle: discover upstream schemas and invoke them. Minor gaps exist around explicit credential status or single-tool metadata, but the list tool returns the necessary schemas for invocation.