Test Public Lunir MCP Server
@MarkO-Lunir
Basic information
About Test Public Lunir MCP Server
testing the lunir mcp servers
Test Public Lunir MCP Server config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTest Public Lunir MCP Server tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is test-public-lunir?
test-public-lunir is a test MCP server used for testing the lunir MCP servers, as indicated by its README.
How to use test-public-lunir?
—
Key features of test-public-lunir?
—
Use cases of test-public-lunir?
—
FAQ from test-public-lunir
—
More Developer Tools MCP servers

GripForge
gripforgeaiThe tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U

Pugi
Pugi Inc.Pugi is an AI product team that builds, checks and publishes websites and apps. Its MCP server gives agents a passive website security check graded A+ to F (headers, TLS, cookies, exposed keys in scripts), free with a no

BetterBugs
BetterBugsThe BetterBugs MCP (Model Context Protocol) enables you to load BetterBugs bug reports (via report links) directly to your preferred AI Agents and developer environments with MCP Client capabilities (such as Cursor, VS C

ArtiBot Cloud MCP - Zhijiangyun 智匠云
bofobArtiBot Cloud MCP (Zhijiangyun 智匠云) — cloud MCP server for robot manipulation data & GPU workloads. 15 tools: robot fleet management, data collection & video recording, post-processing pipelines, and benchmark evaluation

Routebase
RoutebaseRoutebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.
Comments