{
"mcpServers": {
"ozzynet-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A sandbox for MCP server prototyping
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 363 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Ozzynet Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This is a prototype where an MCP server offers tools, but limits their access based on internal state, requiring the user to authenticate via an external url.
In this case, the external url is wrappered with quarkus oidc, requiring authentication via github
The resulting access token for github is then stored within the mcp for the sessionid used by the user
Note: you must edit application.properties to add your client-id and secret for your GitHub OAuth app.
Navigate to https://github.com/settings/developers
Select OAuth Apps from the left nav
Click 'New OAuth App'
Give it a name, and set the callback url to be http://127.0.0.1:8080/auth
Copy the client ID to application.properties Click 'generate a new client secret' and copy the secret to application.properties
Update claude desktop config json...
For windows...
{
"mcpServers": {
"ozzynet": {
"command": "cmd",
"args": [
"/c",
"C:\\Users\\YOURUSERNAME\\.jbang\\bin\\jbang.cmd",
"--quiet",
"org.ozzy:stiletto:1.0.0-SNAPSHOT:runner" ]
}
}
}
For mac...
{
"mcpServers": {
"ozzynet": {
"command": "jbang",
"args": [
"--quiet",
"org.ozzy:stiletto:1.0.0-SNAPSHOT:runner" ]
}
}
}
Ask claude to list the issues for a repository ..
eg, list the issues for quarkusio's quarkus repo
Claude will ask permission to invoke the getSessionId tool Claude will then invoke the listIssues tool, and report it cannot use it, because you need to be authenticated, and will offer you a link of the form http://127.0.0.1/auth?sessionId= .. when you click that, you will be redirected to github, to authorize via the OAuthApp you created. When auth is complete, you can return to claude, and retry the list operation =)