Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.greenmtnsun/wikimint

REMOTE · WIKIMINT.GRAYOCEAN-4062AD43.EASTUS.AZURECONTAINERAPPS.IO

Generate wiki docs from source code. Supports PowerShell, Python, Go, C#, Java, COBOL.

+4 this week 73 Trust /100

Last scanned (22 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability84
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 382 tokens (~127/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://wikimint.grayocean-4062ad43.eastus.azurecontainerapps.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=grayocean-4062ad43.eastus.azurecontainerapps.io,O=Microsoft Corporation,L=Redmond,ST=WA,C=US CN=Microsoft TLS G2 RSA CA OCSP 16,O=Microsoft Corporation,C=US 16 Nov 2026 24 Feb 2027 RSA 2048 SHA384-RSA 55015cc971e87a6ef496e88c2b0000015cc971
SANs: *.grayocean-4062ad43.eastus.azurecontainerapps.io, *.scm.grayocean-4062ad43.eastus.azurecontainerapps.io, *.internal.grayocean-4062ad43.eastus.azurecontainerapps.io, *.ext.grayocean-4062ad43.eastus.azurecontainerapps.io, grayocean-4062ad43.eastus.azurecontainerapps.io
CN=Microsoft TLS G2 RSA CA OCSP 16,O=Microsoft Corporation,C=US (CA) CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US 1 Aug 2025 3 Jun 2029 RSA 4096 SHA384-RSA 330000000e42938f25dc51a99b00000000000e
CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 21 May 2025 19 Jun 2029 RSA 4096 SHA384-RSA b0c6b2c466917b04773c647d4afc0c8
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of wikimint.grayocean-4062ad43.eastus.azurecontainerapps.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
azurecontainerapps.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://wikimint.grayocean-4062ad43.eastus.azurecontainerapps.io/mcp Verified 200
http (plaintext) http://wikimint.grayocean-4062ad43.eastus.azurecontainerapps.io/mcp HTTPS enforced 301 https://wikimint.grayocean-4062ad43.eastus.azurecontainerapps.io/mcp
MCP tools · 3 exposed · ~382 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
generate_wiki ~192

Generates wiki docs — parameters, risk posture, Markdown pages — from source code; eliminates documentation drift that costs engineers hours per sprint. Use when a module ships undocumented or its docs lag. WHEN NOT TO USE: snippets under 5 lines; files with no public functions. Languages: PowerShell, Python, Go, CSharp, Java, COBOL. Use async=true for large files; poll with get_generation_status.

NameTypeReqDescription
asyncboolean–When true, returns a job_id immediately and processes in the background. Default false (synchronous).
codestringyesRaw source code to document. Max 1 MB.
languagestringyesSource language. One of: PowerShell, Python, Go, CSharp, Java, COBOL.
module_namestring|null–Optional display name used as the wiki page title. When omitted, a name is inferred from the code.
NameTypeReqDescription
_metaobject|null––
available_languagesarray|null––
elapsed_msintegeryes–
errorstring|null––
error_codestring|null––
job_idstring|null––
retryableboolean|null––
statusstringyes–
wiki_docobject|null––

No examples provided.

get_generation_status ~111

Returns the current status of an async wiki generation job. Call after generate_wiki with async=true; spares the calling agent or CI pipeline a blocking wait while a large module renders. WHEN NOT TO USE: do not poll for synchronous results — omit async=true on generate_wiki instead. Returns job_id, status (pending/complete/failed), wiki_doc (when complete), error (when failed).

NameTypeReqDescription
job_idstringyesJob ID returned by a prior generate_wiki call with async=true.

No output schema declared.

No examples provided.

get_supported_languages ~79

Returns the current source-language list with harvester metadata. Call instead of hardcoding language names — spares the integrator a silent failure when the supported set grows in a later version. WHEN NOT TO USE: do not call on every generate_wiki invocation; cache the result. Returns languages[] — each entry has name, version, harvester.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.greenmtnsun/wikimint MCP server?

io.github.greenmtnsun/wikimint is a hosted endpoint at https://wikimint.grayocean-4062ad43.eastus.azurecontainerapps.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · wikimint.grayocean-4062ad43.eastus.azurecontainerapps.io

# add to Claude Code
claude mcp add --transport http greenmtnsun-wikimint 'https://wikimint.grayocean-4062ad43.eastus.azurecontainerapps.io/mcp'
Common questions

What is the io.github.greenmtnsun/wikimint MCP server?

io.github.greenmtnsun/wikimint is an MCP server listed in the public MCP registry as io.github.greenmtnsun/wikimint. Generate wiki docs from source code. Supports PowerShell, Python, Go, C#, Java, COBOL. This page covers its hosted endpoint (https://wikimint.grayocean-4062ad43.eastus.azurecontainerapps.io/mcp).

Is the io.github.greenmtnsun/wikimint MCP server safe to use?

io.github.greenmtnsun/wikimint scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.greenmtnsun/wikimint MCP server expose?

io.github.greenmtnsun/wikimint exposes 3 tools: get_supported_languages, get_generation_status, generate_wiki. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.

Does the io.github.greenmtnsun/wikimint MCP server require authentication?

No. We connected to io.github.greenmtnsun/wikimint without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.greenmtnsun/wikimint MCP server still maintained?

io.github.greenmtnsun/wikimint is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.greenmtnsun/wikimint MCP server?

VerifyMCP ran 12 checks on io.github.greenmtnsun/wikimint, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.greenmtnsun/wikimint: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.