Hzpppy

Created By
h5bp10 months ago
Overview

what is Hzpppy?

Hzpppy is a repository containing a collection of front-end interview questions designed to assist in evaluating potential candidates for front-end developer positions.

how to use Hzpppy?

To use Hzpppy, simply browse through the repository and select questions relevant to the skills you wish to assess in candidates. You can choose from various categories such as HTML, CSS, JavaScript, and more.

key features of Hzpppy?

  • Comprehensive collection of front-end interview questions
  • Categorized questions for easy navigation
  • Open-ended questions that encourage discussion

use cases of Hzpppy?

  1. Preparing for front-end developer interviews
  2. Vetting candidates for front-end development roles
  3. Enhancing interview processes with structured questions

FAQ from Hzpppy?

  • Can I use all questions on a single candidate?

It is not recommended to use every question on the same candidate as it may take too long. Select a few relevant questions instead.

  • Are the questions suitable for all experience levels?

Yes! The questions range from basic to advanced, catering to various experience levels.

Server Config

{
  "mcpServers": {
    "mcp_server_redis": {
      "url": "http://10.239.121.20:31854/sse"
    }
  }
}
Project Info
Created At
10 months ago
Updated At
9 months ago
Author Name
h5bp
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago