Ohio State API
v0.1.0Access public Ohio State University campus data from services like bus, dining, events, buildings, parking, and more via osu content APIs in JSON format.
⭐ 0· 1.3k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and SKILL.md describe fetching public Ohio State content APIs and the included code implements tools that only call content.osu.edu endpoints. The package.json and source files match the stated MCP server purpose. (Registry metadata lacked a short description, but the SKILL.md provides the expected purpose.)
Instruction Scope
Runtime instructions only show (a) running the bundled node fetch helper or (b) building/running the provided MCP server; all examples target content.osu.edu. The instructions do not request reading unrelated files or environment variables. Note: the directory/person-search endpoints can return personal directory data — that is expected for the stated purpose but has privacy implications you should consider.
Install Mechanism
No install spec in the registry (instruction-only), but source includes a Node project. Building requires npm install and tsc; dependencies are standard npm packages (lockfile present). No downloads from arbitrary URLs or extract operations were observed.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. That is proportional to its functionality (public HTTP fetches).
Persistence & Privilege
always is false and the skill does not request special platform privileges. Running the MCP server is a normal local service; nothing in the files attempts to modify other skills or system-wide agent settings.
Assessment
This skill appears to do exactly what it says: query public OSU content endpoints via a small Node-based MCP server or a fetch script. Before installing or running: (1) review and run npm install/build in a controlled environment (npm packages will be pulled from public registries), (2) be aware that directory/person-search tools query public directory data (consider privacy/usage policies), and (3) if you will expose the MCP server to other software, run it in a network-limited sandbox or inspect the server code yourself to confirm it only calls content.osu.edu. If you need a minimal footprint, use the curl examples or the single-node fetch script rather than running the full server.Like a lobster shell, security has layers — review code before you run it.
latestvk97854kv7fcet5zypk1zk5vafh80qn0h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.