Skip to main content
Glama
monsunic

Nusawave MCP Server

Official
by monsunic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NUSAWAVE_MCP_NAMENoFastMCP server name (set per config entry)nusawave
NUSAWAVE_SITE_URLNoLive site base URL; required for audit_live_site tool
NUSAWAVE_REPO_PATHNoLocal clone path for this server process.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_repo_overviewA

Return README and key root files for the configured local repository.

list_docsA

List markdown files under docs/ in the local repo.

Args:
    pattern: Glob relative to docs/ (default: all markdown files).
read_repo_fileA

Read a file from the configured local repository.

Args:
    relative_path: Path relative to repo root, e.g. docs/index.md or zensical.toml
    max_chars: Maximum characters to return (default 50000)
fetch_public_pageA

Fetch a public web page (no API key). Good for GitHub Pages sites.

Args:
    page_url: Full URL, e.g. https://nusawave-labs.github.io/
    extract_text: If true, strip HTML to readable text (default true)
audit_live_siteB

Fetch the live site homepage and key section pages as plain text.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct purpose: live site auditing, generic page fetching, repo overview, doc listing, and file reading. No two tools have overlapping functionality.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (audit_live_site, fetch_public_page, get_repo_overview, list_docs, read_repo_file), making them predictable.

Tool Count5/5

With only 5 tools, the server is tightly scoped to auditing and repository access. Each tool is necessary and the count fits the domain well.

Completeness4/5

Core operations for auditing (live site fetch, repo docs, file reading) are covered. Minor gaps exist, such as a dedicated comparison tool, but agents can combine existing tools to achieve similar results.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources